search for: cbe_generated_file

...e C backend cannot include any > system headers. If the system header were to have a #define (not a rare > occurance) the header could arbitrarily change the CBE code in BAAD ways. > :( I was thinking of Eric doing something like: myfile.c: #include <string.h> #include "cbe_generated_file.c" Although, why he would eludes me. Reid. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part URL: <http://lists.llvm.org/pipermail/llvm-dev/attach...

On Wed, 14 Apr 2004, Reid Spencer wrote: > The only thing I can think of is that string.h is being #included and > has different signatures for memcpy and strncpy. Possibly "char" is not > signed on your machine (very unusual) or some of the parameters are > declared as "const". The problem is that the code generated by the C backend cannot include any system

...stem headers. If the system header were to have a #define (not a rare > > occurance) the header could arbitrarily change the CBE code in BAAD ways. > > :( > > I was thinking of Eric doing something like: > > myfile.c: > #include <string.h> > #include "cbe_generated_file.c" > > Although, why he would eludes me. You don't need to do this to get those annoying GCC warnings. They come out whenever you compile a C program produced by the LLVM CBE that uses certain GCC "builtins", like memcpy... :( -Chris -- http://llvm.cs.uiuc.edu/ http://...