search for: cc1

...lvm/projects/test-suite/SingleSource/UnitTests' make[3]: Entering directory '/llvm/projects/test-suite/SingleSource/UnitTests/Vector' make[4]: Entering directory '/llvm/projects/test-suite/SingleSource/UnitTests/Vector/SSE' Compiling sse.expandfft.c to Output/sse.expandfft.bc cc1: warning: unrecognized gcc debugging option: i cc1: warning: unrecognized gcc debugging option: s cc1: warning: unrecognized gcc debugging option: b cc1: warning: unrecognized gcc debugging option: l cc1: warning: unrecognized gcc debugging option: e cc1: warning: unrecognized gcc debugging option:...

> Any ideas? Most likely it is the gcc folder doing it. This gcc optimization is run in llvm-gcc because it's basically impossible to turn it off! You can check by passing -mllvm -disable-llvm-optzns to llvm-gcc along with -O2. If the optimization still occurs then it was gcc that did it. Ciao, Duncan.

Hi Duncan, Thanks for your help. But seems "opt -std-compile-opts" can't do this simplication :( Any ideas? Sheng. 2008/9/4 Duncan Sands <baldrick at free.fr> > > I tried several passes, like -instcombine, -simplifycfg, -gcse -globaldce > > -globalopt -adce , but all failed to do this transform. > > Try "opt -std-compile-opts

Current dragonegg svn builds against llvm svn again, but the resulting dragonegg plugin fails at runtime. When either c or fortran is compiled against either gcc-4.5.3 or gcc-4.6.1, the compilations fail as... cc1: Unknown command line argument '--code-model=default'. Try: 'cc1 -help' cc1: Did you mean '-fast-isel=default'?

...mmar/scfg/scfg.mak WFST grammar/wfst/wfst.mak OLS stats/ols.mak RXP rxp/rxp.mak LINUX16_AUDIO config/modules/linux16_audio.mak Making in directory ./siod ... making dependencies -- siodeditline.c cc1: warning: "-Wno-non-template-friend" is valid for C++ but not for C/ObjC cc1: warning: "-Wno-deprecated" is valid for C++ but not for C/ObjC el_complete.c cc1: warning: "-Wno-non-template-friend" is valid for C++ but not for C/ObjC cc1: warning: "-Wno-deprecated...

On Jan 23, 2013, at 4:04 , "Benyei, Guy" <guy.benyei at intel.com> wrote: > Hi Ankur, > Since you use –Xclang, the clang executable passes multiple triples to “clang -cc1”. You can see that if you add the -v option. I’m sure there is someone here who can explain it better than I… > Anyhow, I think you better use clang -cc1. Make sure -cc1 is the first command line option you use. > > $ clang -cc1 -fno-builtin -emit-llvm-bc -triple spir-unknown-unknown Sim...

As of LLVM 3.2, is it possible to use iostream with the MCJIT or interpreter execution engines? I'm getting some errors... Each of these commands correctly prints "hello": echo -e '#include <stdio.h>\nint main(){ printf("hello"); }' | clang -cc1 -emit-llvm-bc -x c++ | lli -use-mcjit echo -e '#include <iostream>\nint main(){ std::cout << "hello" << std::endl; }' | clang -cc1 -emit-llvm-bc -x c++ | lli Each of these commands results in "LLVM ERROR: Could not resolve external global address: __dso_...

...ith the new build system. Arch Linux meson-0.55.1 Overall, it looks good, so well done! Just a couple of minor things I noted: 1. Arch uses a meson wrapper script (arch-meson) that sets:   --buildtype plain This seems to trigger a bug in meson that results in copious bogus compiler warnings: cc1: warning: ‘-Wformat-y2k’ ignored without ‘-Wformat’ [-Wformat-y2k] cc1: warning: ‘-Wformat-extra-args’ ignored without ‘-Wformat’ [-Wformat-extra-args] cc1: warning: ‘-Wformat-zero-length’ ignored without ‘-Wformat’ [-Wformat-zero-length] cc1: warning: ‘-Wformat-contains-nul’ ignored without ‘-Wfor...

Hi Jack, > Current dragonegg svn builds against llvm svn again, but the resulting > dragonegg plugin fails at runtime. When either c or fortran is compiled > against either gcc-4.5.3 or gcc-4.6.1, the compilations fail as... > > cc1: Unknown command line argument '--code-model=default'. Try: 'cc1 -help' > cc1: Did you mean '-fast-isel=default'? I didn't catch up with all the LLVM changes yet. Probably I will today. Ciao, Duncan.

...uments/School/Thesis/work/install/psptoolchain/lib/gcc/psp/4.1.0/include -c -emit-llvm -Wall \ -D_PSP_FW_VERSION=150 -DPSP=1 -D__psp__=1 -D_PSP=1 -I/home/kevin/Documents/School/Thesis/work/install/psptoolchain/psp/sdk/include -O1 main.c -o main.o llvm-gcc: error trying to exec 'cc1': execvp: No such file or directory When I ran "make -k install" it looked like every invocation of xgcc died with an abort (after throwing std::bad_alloc). Something serious happening here? Regards, Kevin André

...l consolidate into 3 questions. For all examples below, I used combo- gcc 4.6 + dragonegg(trunk) + llvm(trunk) (1). Does 'fplugin-arg-dragonegg-llvm-option' allow all 'opt' options? $ gcc -fplugin=dragonegg.so -fplugin-arg-dragonegg-llvm-option='-disable-inlining' foo.c -S cc1: Unknown command line argument '-disable-inlining'. Try: 'cc1 -help' (2). Does 'fplugin-arg-dragonegg-llvm-option' allow ONLY 'opt' options? (by llvm options does it mean only opt) (3). Depending on answer to (2), currently is there a way to pass llc options to...

...toolchain/lib/ > gcc/psp/4.1.0/include > -c -emit-llvm -Wall \ > -D_PSP_FW_VERSION=150 -DPSP=1 -D__psp__=1 -D_PSP=1 > -I/home/kevin/Documents/School/Thesis/work/install/psptoolchain/psp/ > sdk/include > -O1 main.c -o main.o > llvm-gcc: error trying to exec 'cc1': execvp: No such file or > directory Do: find . -name cc1 -print to find cc1 in the build directory. Then, copy this file by hand to to llvm-gcc -print-prog-name=cc1.

Hi, I am trying to build llvm-gcc from svn and I am getting a "cc1: error: unrecognized command line option "-Wno-overlength-strings"" error. I have gcc 4.1.2 and Linux 2.6.18 on 64bit. Please tell me how to fix this error. Here is the command that caused this: gcc -c -g -O2 -DIN_GCC -W -Wall -Wwrite-strings -Wstrict-prototypes -Wmissing-proto...

...v at cs.uiuc.edu Subject: Re: [cfe-dev] OpenCL SPIR/NVPTX code generation On Jan 23, 2013, at 4:04 , "Benyei, Guy" <guy.benyei at intel.com<mailto:guy.benyei at intel.com>> wrote: Hi Ankur, Since you use -Xclang, the clang executable passes multiple triples to "clang -cc1". You can see that if you add the -v option. I'm sure there is someone here who can explain it better than I... Anyhow, I think you better use clang -cc1. Make sure -cc1 is the first command line option you use. $ clang -cc1 -fno-builtin -emit-llvm-bc -triple spir-unknown-unknown Simple_K...

Hi, I am quite new to LLVM. I just compiled LLVM and clang on Ubuntu11.10 then followed the tutorial http://llvm.org/docs/DebuggingJITedCode.html clang -cc1 -O0 -g -emit-llvm showdebug.c where showdebug.c contains: #include<stdio.h> int main() { printf("hello\n"); return 0; } But I got Fatal error: 'stdio.h' file not found. However, clang showdebug.c has no problem. I know -g means to generate debug information, -em...

...one! >> >> Just a couple of minor things I noted: >> >> 1. Arch uses a meson wrapper script (arch-meson) that sets: >> >>   --buildtype plain >> >> This seems to trigger a bug in meson that results in copious bogus compiler warnings: >> >> cc1: warning: ‘-Wformat-y2k’ ignored without ‘-Wformat’ [-Wformat-y2k] >> cc1: warning: ‘-Wformat-extra-args’ ignored without ‘-Wformat’ [-Wformat-extra-args] >> cc1: warning: ‘-Wformat-zero-length’ ignored without ‘-Wformat’ [-Wformat-zero-length] >> cc1: warning: ‘-Wformat-contains-...

Yes,but ubuntu's directory structure is not exactly the same as the classic linux distribute, I put libLLVMgold.so in /usr/lib/gcc/i486-linux-gnu/4.2.4 where cc1 is also in. Strange situation,is it a bug for llvm-gcc???? 在 2009-09-18五的 12:58 +0300，Török Edwin写道： > On 2009-09-18 03:06, Nan Zhu wrote: > > OMG,that's just my situation... > > > > I can link with libLLVMgold.so manualy,but will fail in that by llvm-gcc. > > &...

Dear Zhang, Compiler ends up invoking cc1 (the backend) anyways. So if you would like to invoke it by hand, the only thing to know is the right combination of options. Try to use the compiler verbose option "-v". It will show you how exactly clang invokes the backend: > clang -v -c showdebug.c clang version 3.2 (trunk 156703)...

...>> > > 1. Arch uses a meson wrapper script (arch-meson) that sets: >> > > >> > >   --buildtype plain >> > > >> > > This seems to trigger a bug in meson that results in copious bogus compiler warnings: >> > > >> > > cc1: warning: ‘-Wformat-y2k’ ignored without ‘-Wformat’ [-Wformat-y2k] >> > > cc1: warning: ‘-Wformat-extra-args’ ignored without ‘-Wformat’ [-Wformat-extra-args] >> > > cc1: warning: ‘-Wformat-zero-length’ ignored without ‘-Wformat’ [-Wformat-zero-length] >> > > cc1...

I've always debugged the backend llc by running it as a separate executable. I'm seeing a bug that only happens when I run the compiler from clang. How do you debug this from gdb? I can put a breakpoint but it never stops when I say "run ...." Tia. Reed