search for: cc1plus

...--with-llvmsrc=/home/foad/svn/llvm-project/llvm/trunk [...] foad at debian:~/svn/llvm-project/test-suite/trunk$ make -C MultiSource/Applications/minisat/ make: Entering directory `/home/foad/svn/llvm-project/test-suite/trunk/MultiSource/Applications/minisat' Compiling Main.cpp to Output/Main.bc cc1plus: warning: unrecognized gcc debugging option: i cc1plus: warning: unrecognized gcc debugging option: s cc1plus: warning: unrecognized gcc debugging option: b cc1plus: warning: unrecognized gcc debugging option: l cc1plus: warning: unrecognized gcc debugging option: e cc1plus: warning: unrecognized g...

...project/llvm/trunk > [...] > foad at debian:~/svn/llvm-project/test-suite/trunk$ make -C > MultiSource/Applications/minisat/ > make: Entering directory > `/home/foad/svn/llvm-project/test-suite/trunk/MultiSource/Applications/minisat' > Compiling Main.cpp to Output/Main.bc > cc1plus: warning: unrecognized gcc debugging option: i > cc1plus: warning: unrecognized gcc debugging option: s > cc1plus: warning: unrecognized gcc debugging option: b > cc1plus: warning: unrecognized gcc debugging option: l > cc1plus: warning: unrecognized gcc debugging option: e > cc1plus...

...-DP_SSL -DP_PTHREADS -DPHAS_TEMPLATES -DPTRACING -DP_USE_PRAGMA -I../../include -I/usr/ports/devel/pwlib/work/pwlib/include/ptlib/unix -I/usr/ports/devel/pwlib/work/pwlib/include -I/usr/ports/net/openh323/work/openh323/include -Wno-missing-prototypes -Wno-missing-declarations ast_h323.cpp cc1plus: warning: command line option "-Wstrict-prototypes" is valid for C/ObjC but not for C++ cc1plus: warning: command line option "-Wmissing-prototypes" is valid for C/ObjC but not for C++ cc1plus: warning: command line option "-Wmissing-declarations" is valid for C/...

Hello, Jay > I guess this is because the test suite is trying to run "llvm-gcc > -mllvm -disable-llvm-optzns", which never seems to work, because > llvm-gcc mangles the command line before it gets to cc1plus. That's correct. The driver changes the order of the options provided. You need to provided this option to cc1 / cc1plus directly > Is it just me having this problem? No. > How can I fix it? No idea, but I guess you can either hack on gcc specs. Or don't use this option at all - thi...

Hi, > > I guess this is because the test suite is trying to run "llvm-gcc > > -mllvm -disable-llvm-optzns", which never seems to work, because > > llvm-gcc mangles the command line before it gets to cc1plus. > That's correct. The driver changes the order of the options provided. > You need to provided this option to cc1 / cc1plus directly Dan fixed this recently in svn IIRC - I don't think it's in the prerelease candidate. > > > Is it just me having this problem? > No....

Hi, I tried to compile LLVM on an Amazon EC2 Linux instance that doesn't have a ton of memory (~600 MB). It keeps failing with: llvm[4]: Compiling ARMAsmParser.cpp for Release build g++: Internal error: Killed (program cc1plus) It's getting killed for using all the system memory. Is this file known to trigger any bugs in gcc? (version 4.1.2) Here is /var/log/messages: Feb 28 13:33:54 ip-10-195-190-127 klogd: [232896.775450] Out of memory: kill process 6740 (cc1plus) score 165582 or a child Feb 28 13:33:54 ip-10-1...

...cpu=i586 -DP_LINUX -D_REENTRANT -DP_HAS_SEMAPHORES -DP_SSL -DP_PTHREADS -DPBYTE_ORDER=PLITTLE_ENDIAN -DPHAS_TEMPLATES -O3 -DNDEBUG -I/usr/include -I/usr/include/crypto -I/root/pwlib/include/ptlib/unix -I/root/pwlib/include -I/root/openh323/include -I../asterisk-driver -g -c wrapper.cxx -o wrapper.o cc1plus: warning: changing search order for system directory "/usr/include" cc1plus: warning: as it has already been specified as a non-system directory wrapper.cxx: In constructor `WrapH323Connection::WrapH323Connection(WrapH323EndPoint&, unsigned int, int, int, short unsigned int)...

...le without >> a major rewriting of LLVM. > > Even with no optimizations? Drat. That means I can't use it. Why? I'd never checked, but I always assumed the LLVM JIT was much larger than 3.4 MB. For comparison: [rnk at tamalpais google3]$ du -h /usr/lib/gcc/x86_64-linux-gnu/4.4/cc1plus 10M /usr/lib/gcc/x86_64-linux-gnu/4.4/cc1plus [rnk at tamalpais google3]$ du -h `which python2.6` 2.5M /usr/bin/python2.6 It seems reasonable that a JIT compiler with optimizers would weigh in somewhere between an interpreter and a full C++ compiler. Reid

...mean "the way you would do it if you believe what it says in the autoconf manual") would be to specify --build=x86_64-unknown-linux --target=alpha-unknown-linux. This produces Makefiles that bomb out on the very first file in the tree: $ make llvm[1]: Compiling Alarm.cpp for Debug build cc1plus: error: unrecognized command line option "-mieee" cc1plus: error: unrecognized command line option "-mieee" because Makefile.config has ARCH=Alpha, and Makefile.rules changes the options passed to the build compiler based on ARCH. IMO this is a bug, but I don't understand...

...LROUND and HAVE_FSEEKO conditional sections, normally resolved elsewhere in the full build system. * Add Makefile variables CCFLAGS and CCCFLAGS to specify gcc-only and g++-only flags, respectively. This was done to eliminate the following warnings, which were repeated for every g++ invocation: >cc1plus.exe: warning: command line option '-Wmissing-prototypes' is valid for C/ObjC but not for C++ [enabled by default] >cc1plus.exe: warning: command line option '-Wstrict-prototypes' is valid for C/ObjC but not for C++ [enabled by default] * Remove inclusion of "include/share&qu...

Grabbed the latest bits from SVN (, tried to build with MinGW. I get a cc1plus.exe out of memory error while trying to "make ENABLE_OPTIMIZED=1" on the X86CodeEmitter. I can get a full stack trace if necessary, but has anybody else run into this problem? Only seems to happen with the Release build-I got a full Debug build to work fine. Ted Neward Java, .NET, XM...

Hi, The gcc version in my system is 3.4.6 During make display error message and stop cc1plus:error: unrecognzied command line option -Wno-variadic-macros Must i update gcc to version 4.2.0 or above to resolve the problem? Thanks -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20091021/980bbe86/attach...

I've built a debug build of llvm 2.6, and llvm-gcc 2.6 for arm-elf with --enable-checking=yes. On the attached test case (which is g++.dg/expr/bitfield4.C from the GCC 4.2 testsuite) I get: $ cc1plus bitfield4.ii -emit-llvm-bc -o bitfield4.o -quiet cc1plus: /home/foad/svn/antix/toolchain/branches/w/foad/2757llvm26/toolchain/llvm/llvm-gcc/gcc/llvm-convert.cpp:999: llvm::Value* TreeToLLVM::Emit(tree_node*, const MemRef*): Assertion `(Result == 0 || (((enum tree_code) (((exp)->common.type))-&g...

Hi, I got the following error message when I try to compile llvm-gcc with gcc 3.4.6: cc1plus: error: unrecognized command line option "-Wno-variadic-macros" make[3]: *** [llvm-main.o] Error 1 Someone have an idea ? thanks ________________________________ This message is confidential and intended only for the addressee. If you have received this message in error, please immedia...

...ested the attached patch. It enables compiling llvm-gcc > for me, but i have not yet done any further testing and i also have no > idea if this is the right way to fix the problem. Nice. I will give it a try. I was trying to reduce a test case, but it is a bit hard. I have a cpp that crashes cc1plus, but the resulting .ll works opt! > > Hope that helps, > > Marco Cheers, Rafael

My nightly tester reports that it failed to bootstrap today: Comparing stages 2 and 3 warning: ./cc1-checksum.o differs warning: ./cc1plus-checksum.o differs Bootstrap comparison failure! ./c-cppbuiltin.o differs ./real.o differs ./build/genautomata.o differs Ciao, Duncan.

...s in the autoconf manual") would be to >> specify --build=x86_64-unknown-linux --target=alpha-unknown-linux. >> This produces Makefiles that bomb out on the very first file in the >> tree: >> >> $ make >> llvm[1]: Compiling Alarm.cpp for Debug build >> cc1plus: error: unrecognized command line option "-mieee" >> cc1plus: error: unrecognized command line option "-mieee" >> >> because Makefile.config has ARCH=Alpha, and Makefile.rules changes the >> options passed to the build compiler based on ARCH.  IMO this is...

...t if you believe what it says in the autoconf manual") would be to > specify --build=x86_64-unknown-linux --target=alpha-unknown-linux. > This produces Makefiles that bomb out on the very first file in the > tree: > > $ make > llvm[1]: Compiling Alarm.cpp for Debug build > cc1plus: error: unrecognized command line option "-mieee" > cc1plus: error: unrecognized command line option "-mieee" > > because Makefile.config has ARCH=Alpha, and Makefile.rules changes the > options passed to the build compiler based on ARCH.  IMO this is a > bug, but...

The previously selected 'atomic' recipe resulted in 2GB swap in a 6GB volume. Also, we don't really need the boot partition, so just create a partition using the whole disk space. --- builder/templates/debian.preseed | 13 ++++++++++++- 1 file changed, 12 insertions(+), 1 deletion(-) diff --git a/builder/templates/debian.preseed b/builder/templates/debian.preseed index

See this bug for background information: https://bugzilla.redhat.com/show_bug.cgi?id=1350465 Thanks: Tomáš Golembiovský --- v2v/virt-v2v.pod | 38 ++++++++++++++++++++++++++------------ 1 file changed, 26 insertions(+), 12 deletions(-) diff --git a/v2v/virt-v2v.pod b/v2v/virt-v2v.pod index e68d75cf8..87dba240b 100644 --- a/v2v/virt-v2v.pod +++ b/v2v/virt-v2v.pod @@ -1909,18 +1909,32 @@ that