search for: string_const

...(which uses 4.3 as version > number). If you need a LLVM front end based on GCC 4.3, please create > separate llvm.org/svn/llvm-project/llvm-gcc-4-3 module. Is back-porting fixes from 4.3 OK? > 5) There are many GCC tree structure changes that I have not noticed > yet. I think STRING_CONSTANT is actually a constant in 4.2, which means all those tests for "is it a constant or a STRING_CONSTANT" in llvm-convert can be simplified. > Note, llvm-gcc-4-2 does not replace llvm-gcc-4-0. Current llvm-gcc FE > (which is based on GCC-4.0) will be added in llvm svn at llvm.org...

In my latest patch, I hardcoded the port NUT uses for TCP communication (3493). The reason is, that I can't figure out a way how to change the numeric value of the #define'd PORT into a character string. Using snprintf() and a temporary buffer just seems wrong, since this should be handled by the preprocessor, rather than at runtime. The following files are affected: - server/conf.c (line

Hi All, llvm-gcc-4-2 development branch is now open for development at llvm.org/svn/llvm-project/llvm-gcc-4-2 It is not yet ready, it can not even bootstrap. I welcome LLVM developers to test and apply fixes! However, first take a note of ground rules : 1) LLVM developers, use your write access as judiciously as you use it for LLVM development and follow same check-in procedure. 2)