search for: builtin_memset

...gcc: you can't always avoid having gcc use the gcc memset builtin. However it has to be said that gcc generates its memset builtin less often than llvm-gcc generates llvm.memset, so this is not as visible. Also (I'm not sure about this) it may be that on some platforms gcc always expands builtin_memset into a code sequence rather than generating a call to the library memset function. However, gcc is not obliged to use a code sequence even in a freestanding environment. The environment is always required to provide memset. Here's what the gcc docs say: GCC requires the freestanding envir...

...always > avoid having gcc use the gcc memset builtin.  However it has to be said > that gcc generates its memset builtin less often than llvm-gcc generates > llvm.memset, so this is not as visible.  Also (I'm not sure about this) > it may be that on some platforms gcc always expands builtin_memset into a > code sequence rather than generating a call to the library memset function. > However, gcc is not obliged to use a code sequence even in a freestanding > environment.  The environment is always required to provide memset.  Here's > what the gcc docs say: > >   GCC req...

Hi, all, I am using llvm-gcc --emit-llvm to generate byte code. With llvm readable ll format, I found some standard C library function such as llvm.memset. In fact, I'm trying to compile newlibc with llvm, I do not need this kind of llvm functions. How can I remove them during the compilation? Best regards, -- Hao Shen

...avoid having gcc use the gcc memset builtin. However it has to be said >> that gcc generates its memset builtin less often than llvm-gcc generates >> llvm.memset, so this is not as visible. Also (I'm not sure about this) >> it may be that on some platforms gcc always expands builtin_memset into a >> code sequence rather than generating a call to the library memset function. >> However, gcc is not obliged to use a code sequence even in a freestanding >> environment. The environment is always required to provide memset. Here's >> what the gcc docs say: &gt...

...gcc use the gcc memset builtin.  However it has to be said >>> that gcc generates its memset builtin less often than llvm-gcc generates >>> llvm.memset, so this is not as visible.  Also (I'm not sure about this) >>> it may be that on some platforms gcc always expands builtin_memset into a >>> code sequence rather than generating a call to the library memset function. >>> However, gcc is not obliged to use a code sequence even in a freestanding >>> environment.  The environment is always required to provide memset.  Here's >>> what the g...