- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Link Copied
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
The ReleaseNotes actually mentioned this specific problem. See below for the details. All you need to do is to use IntelC's linker.
Jennifer
Fast Memory Copy Routines
The following is only an issue if you are not linking against the standard Intel libraries, either as a result of specifying -nostdlib
on the command line or as a result of calling the linker directly rather than from the Intel C++ Compiler driver.
The Intel C++ Compiler uses two routines _intel_fast_memcpy
and _intel_fast_memset
to perform memcpy and memset operations that are not macro expanded to __builtin_memcpy
and __builtin_memset
in the source code. These are found in libirc
. If you use the gcc
compiler to link your application or if you directly call the linker, ld
, you might find these unresolved symbols. For this reason, Intel recomends using the Intel C++ Compiler for linking, using the same compiler options used during the compilation phase. However, if you see these as undefined externals, either add -lirc
to your link line, or change your includes so that memcpy
and memset
will be macro expanded to the builtin forms and recompile. The Intel C++ Compiler for IA-32 based applications calls a routine intel_proc_init
from the main routine of any program to ensure that the processor is correctly set up. This routine is also found in libirc
. These routines used further entry points from glibc
, so -lirc
needs to be placed before -lc
on your command line.

- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page