про все эти префиксы (nptr, gnueabi, и пр)? Есть какое-то соглашение о наименовании или типа сиди сам гадай?
я бы тут почитал http://crosstool-ng.github.io сам только с HF и без него под ARM билдил. Собственно если флоты эмулированные, а в коде их много то исполнение будет дорогое. https://www.linux.org.ru/forum/development/10188780 - вот тут еще есть переписка: Если тулчейн не для arm-архитектуры, то EABI/ABI, обычно, опускается. И пишется просто -uclibc-, -gnu- или вообще -elf-.
Сразу тогда вопрос в космос - чем EABI от ABI отличается?
Complete ABIs A complete ABI, such as the Intel Binary Compatibility Standard (iBCS),[1] allows a program from one operating system supporting that ABI to run without modifications on any other such system, provided that necessary shared libraries are present, and similar prerequisites are fulfilled. Other[which?] ABIs standardize details such as the C++ name mangling,[2] exception propagation,[3] and calling convention between compilers on the same platform, but do not require cross-platform compatibility. Embedded ABIs An embedded-application binary interface (EABI) specifies standard conventions for file formats, data types, register usage, stack frame organization, and function parameter passing of an embedded software program, for use with an embedded operating system. Compilers that support the EABI create object code that is compatible with code generated by other such compilers, allowing developers to link libraries generated with one compiler with object code generated with another compiler. Developers writing their own assembly language code may also interface with assembly generated by a compliant compiler. EABIs are designed to optimize for performance within the limited resources of an embedded system. Therefore, EABIs omit most abstractions that are made between kernel and user code in complex operating systems. For example, dynamic linking may be avoided to allow smaller executables and faster loading, fixed register usage allows more compact stacks and kernel calls, and running the application in privileged mode allows direct access to custom hardware operation without the indirection of calling a device driver. [4] The choice of EABI can affect performance.[5][6] Widely used EABIs include PowerPC,[4] Arm EABI[7] and MIPS EABI.[8] Specific software implementations like the C library may impose additional limitations to form more concrete ABIs; one example is the GNU OABI and EABI for ARM, both of which are subsets of the ARM EABI .[9] https://en.wikipedia.org/wiki/Application_binary_interface#EABI
Да, спасибо, как-то я не удосужился в википедию заглянуть, сорри)
Сам плотно с этим не работал - не подскажу что может пойти не так. Про 'nptl' слышу первый раз - если разберешься напиши - интересно
Обсуждают сегодня