Result for E3A5FE6046906A11D9F39E79D9E2E19FC28340EE

Query result

Key Value
FileName./usr/lib/.build-id/33/360bc7f499b086a6088adbf9bdc879274589bf
FileSize37
MD5FA43CE2C772AB78D369F4C41ABD77BDD
SHA-1E3A5FE6046906A11D9F39E79D9E2E19FC28340EE
SHA-256E0EF40AA60326A7587B557208A8575BAF8341668004CD30804CFB378664B0C7B
SSDEEP3:gCD/Wln:X/Wln
TLSH
hashlookup:parent-total2
hashlookup:trust60

Network graph view

Parents (Total: 2)

The searched file hash is included in 2 parent files which include package known and seen by metalookup. A sample is included below:

Key Value
MD597C22CFC85FB3F5ED89DBA7A6CF14086
PackageArchx86_64
PackageDescriptionCompilers for high level languages generate code that follow certain conventions. These conventions are necessary, in part, for separate compilation to work. One such convention is the "calling convention". The calling convention is a set of assumptions made by the compiler about where function arguments will be found on entry to a function. A calling convention also specifies where the return value for a function is found. Some programs may not know at the time of compilation what arguments are to be passed to a function. For instance, an interpreter may be told at run-time about the number and types of arguments used to call a given function. `Libffi' can be used in such programs to provide a bridge from the interpreter program to compiled code. The `libffi' library provides a portable, high level programming interface to various calling conventions. This allows a programmer to call any function specified by a call interface description at run time. FFI stands for Foreign Function Interface. A foreign function interface is the popular name for the interface that allows code written in one language to call code written in another language. The `libffi' library really only provides the lowest, machine dependent layer of a fully featured foreign function interface. A layer must exist above `libffi' that handles type conversions for values passed between the two languages.
PackageMaintainerumeabot <umeabot>
PackageNamelib64ffi6
PackageRelease7.mga7
PackageVersion3.2.1
SHA-142212548EEB0EE2619279F939D505D95BFA95FEA
SHA-25677367590766BBD2DD9B145E88E3B9E30BC2B4A84917D6E5D9D651152EB1D8A33
Key Value
MD5F2994C4FE2590B5666F584CAB038E760
PackageArchaarch64
PackageDescriptionCompilers for high level languages generate code that follow certain conventions. These conventions are necessary, in part, for separate compilation to work. One such convention is the "calling convention". The calling convention is a set of assumptions made by the compiler about where function arguments will be found on entry to a function. A calling convention also specifies where the return value for a function is found. Some programs may not know at the time of compilation what arguments are to be passed to a function. For instance, an interpreter may be told at run-time about the number and types of arguments used to call a given function. `Libffi' can be used in such programs to provide a bridge from the interpreter program to compiled code. The `libffi' library provides a portable, high level programming interface to various calling conventions. This allows a programmer to call any function specified by a call interface description at run time. FFI stands for Foreign Function Interface. A foreign function interface is the popular name for the interface that allows code written in one language to call code written in another language. The `libffi' library really only provides the lowest, machine dependent layer of a fully featured foreign function interface. A layer must exist above `libffi' that handles type conversions for values passed between the two languages.
PackageMaintainerumeabot <umeabot>
PackageNamelib64ffi6
PackageRelease7.mga7
PackageVersion3.2.1
SHA-1DDE95892926AEAC0FD5BF381CF072AD4AAAE9DA4
SHA-256D5540BA4E615B5E52D39A4093A421B8BC2589D2179922C355148A30E901B7C0B