search for: cc1as

...ns-armv6m.dir/arm/aeabi_memcmp.S.o -MF projects/compiler-rt/lib/builtins/CMakeFiles/clang_rt.builtins-armv6m.dir/arm/aeabi_memcmp.S.o.d -o projects/compiler-rt/lib/builtins/CMakeFiles/clang_rt.builtins-armv6m.dir/arm/aeabi_memcmp.S.o -c ../projects/compiler-rt/lib/builtins/arm/aeabi_memcmp.S clang -cc1as: fatal error: error in backend: unsupported relocation on symbol [1917/5024] Building ASM object projects/compiler-rt/lib/built.../CMakeFiles/clang_rt.builtins-armv6m.dir/arm/aeabi_memmove.S.o FAILED: projects/compiler-rt/lib/builtins/CMakeFiles/clang_rt.builtins-armv6m.dir/arm/aeabi_memmove.S.o /u...

...this is supposed to work because as far as I understood LTOModule::addAsmGlobalSymbols only creates a RecordStreamer which is then attached to the MCTargetAsmParser, and no TargetStreamer is ever created. The places that explicitly call createAsmStreamer are only writing assembly as llvm-mc or cc1as. I've tried to follow that scheme in addAsmGlobalSymbols but failed. Any ideas? Andrey

Hi Eric, It's the unsolved problems on the pass-MCTargetOptions-everywhere path that are my main concern with that approach rather than the amount of work. The first problem is that the result of IRObjectFile::CollectAsmUndefinedRefs() depends on the ABI but IRObjectFile doesn't know it. How would you deliver the ABI to IRObjectFile? The second problem is that IRLinker will link

...r 'fildl') fild 8(%esi,%edi,2) ^ The gcc/config.log shows that the configure test for the filds and fists mnemonics fails with... configure:24880: checking assembler for filds and fists mnemonics configure:24889: /usr/bin/as -o conftest.o conftest.s >&5 clang -cc1as: fatal error: error in backend: 32-bit absolute addressing is not supported in 64-bit mode configure:24892: $? = 1 configure: failed program was filds mem; fists mem The same behavior is seen with in-line assembly in clang 3.7svn... % cat conftest.c asm("filds mem; fists mem"); % clang-...

Hi, Having recently enabled IAS by default for the MIPS O32 ABI, I'm now trying to do the same thing for the MIPS N64 ABI. Unfortunately, it is not currently possible to enable IAS by default for the N64 ABI without also enabling it for the N32 ABI because this information is not reflected in the triple and that's the only information MipsMCAsmInfo has. This would be fine if it N32 was

...386>type sqrt.c float __cdecl sqrt(float z) { return 0.0; } H:\CI\bld\compilers\musl\src\math\i386>clang -integrated-as -c -v --target=i686 -pc-win32 sqrt.s clang version 3.4 (trunk) Target: i686-pc-win32 Thread model: posix "C:\Program Files (x86)\LLVM 3.4.svn\bin\clang.exe" -cc1as -triple i686-pc-win3 2 -filetype obj -main-file-name sqrt.s -target-cpu pentium4 -fdebug-compilation- dir "H:\\CI\\bld\\compilers\\musl\\src\\math\\i386" -dwarf-debug-producer clang version 3.4 (trunk) -o sqrt.o sqrt.s H:\CI\bld\compilers\musl\src\math\i386>llvm-objdump -s -r -t sqrt....

Thanks for pointing this out. The following is a more extensive test. //succeed means dumping help info without Error message. clang -help #succeed 'clang -help-hidden' #Fail 'clang --help-hidden' #Succeed clang -mllvm -v -help #Succeed clang -mllvm -v -help-hidden #Fail clang -mllvm -v --help-hidden #Succeed 'clang -mllvm -help -c LULESH.cc' #Succeed 'clang -mllvm

...; { > return 0.0; > } > H:\CI\bld\compilers\musl\src\math\i386>clang -integrated-as -c -v > --target=i686 > -pc-win32 sqrt.s > clang version 3.4 (trunk) > Target: i686-pc-win32 > Thread model: posix > "C:\Program Files (x86)\LLVM 3.4.svn\bin\clang.exe" -cc1as -triple > i686-pc-win3 > 2 -filetype obj -main-file-name sqrt.s -target-cpu pentium4 > -fdebug-compilation- > dir "H:\\CI\\bld\\compilers\\musl\\src\\math\\i386" -dwarf-debug-producer > clang > version 3.4 (trunk) -o sqrt.o sqrt.s > > H:\CI\bld\compilers\musl\src\m...

On 3/17/15 3:19 PM, Steve King wrote: > Doesn't count for much, but I'm sympathetic to Dario's concern with > cl::opt and clang defaults. In one large out-of-tree project, > colleagues decided to create their own driver to handle the required > customization of the build process and options. > > If clang is the user's one stop shop, here's one such cross

...fatbin" which, from my understanding, compiles the host code in tests/axpy.cu and link it with axpy-sm_30.fatbin. However, now that I instrumented the IR of the host code (axpy.bc) and did `llc axpy.bc -o axpy.s`, which cmd should I use to link axpy.s with axpy-sm_30.fatbin? I tried to use -cc1as, but the flag '-fcuda-include-gpubinary' was not recognized. Thanks! yuanfeng On Sat, Mar 12, 2016 at 12:05 AM, Jingyue Wu <jingyue at google.com> wrote: > I've no idea. Without instrumentation, nvvm_reflect_anchor doesn't appear > in the final PTX, right? If that...

...; } >> H:\CI\bld\compilers\musl\src\math\i386>clang -integrated-as -c -v >> --target=i686 >> -pc-win32 sqrt.s >> clang version 3.4 (trunk) >> Target: i686-pc-win32 >> Thread model: posix >> "C:\Program Files (x86)\LLVM 3.4.svn\bin\clang.exe" -cc1as -triple >> i686-pc-win3 >> 2 -filetype obj -main-file-name sqrt.s -target-cpu pentium4 >> -fdebug-compilation- >> dir "H:\\CI\\bld\\compilers\\musl\\src\\math\\i386" -dwarf-debug-producer >> clang >> version 3.4 (trunk) -o sqrt.o sqrt.s >> >&gt...

...y understanding, compiles the host code in tests/axpy.cu >> and link it with axpy-sm_30.fatbin. However, now that I instrumented the >> IR of the host code (axpy.bc) and did `llc axpy.bc -o axpy.s`, which cmd >> should I use to link axpy.s with axpy-sm_30.fatbin? I tried to use -cc1as, >> but the flag '-fcuda-include-gpubinary' was not recognized. >> >> Thanks! >> >> yuanfeng >> >> On Sat, Mar 12, 2016 at 12:05 AM, Jingyue Wu <jingyue at google.com> wrote: >> >>> I've no idea. Without instrumentation, nvv...

Thanks, Craig. So, clang -Xclang -disable-llvm-passes actually disables all the LLVM passed populated by clang so that there is no middle-end optimization on bc files. clang -O2 LULESH.c //clang is the driver, invoking cc1, cc1as, ld //options can be passed through to cc1 directly. //maybe have different names, e.g. -fvectorize in clang driver and -vectorize-loops in clang -cc1 //options are dumped by clang -help and cla...

...t;wenwangtoddy at gmail.com> wrote: > Thanks, Craig. > > So, clang -Xclang -disable-llvm-passes actually disables all the LLVM > passed populated by clang so that there is no middle-end optimization on bc > files. > > clang -O2 LULESH.c //clang is the driver, invoking cc1, cc1as, ld > //options can be passed through to cc1 > directly. > //maybe have different names, e.g. > -fvectorize in clang driver and -vectorize-loops in clang -cc1 > //options are dump...

Yes that is what he meant. "-dce, -adce, etc" are command line options consumed by tools/opt/opt.cpp to give to the PassManagerBuilder that it creates. The parsing of those options doesn't exist in any of the llvm library code that is linked into clang. Clang has its own code for populating a PassManagerBuilder in tools/clang/lib/CodeGen/BackendUtil.cpp ~Craig On Mon, Jan 8, 2018

Hi, I am trying to compare the loop vectorizers effectiveness for different targets relative to each other. That way, I am hoping to find loops that are not vectorized - but could be - on my target by finding other targets doing this successfully. With some luck, there might be something in the Target files that could be fixed with improved vectorization as a result... I would like to do

On Mon, Mar 19, 2018 at 1:52 PM Jake Ehrlich via llvm-dev < llvm-dev at lists.llvm.org> wrote: > > Is there a typo somewhere in there? "llvm-as" and "GNU as" are completely > unrelated. > > It wasn't a typo unfortunately but I should have said llvm-mc. I just > googled "llvm as" saw "llvm-as" and thought "oh that must be

...e/mahesha/Scratch -ferror-limit 19 -fmessage-length 211 -fobjc-runtime=gcc -fdiagnostics-show-option -fcolor-diagnostics -o hello.s -x ir hello.bc -faddrsig clang -cc1 version 9.0.0 based upon LLVM 9.0.0svn default target x86_64-unknown-linux-gnu "/home/mahesha/LLVM/install/bin/clang-9" -cc1as -triple x86_64-unknown-linux-gnu -filetype obj -main-file-name hello.cpp -target-cpu x86-64 -dwarf-version=4 -mrelocation-model static -mrelax-all -o hello.o hell o.s "/usr/bin/ld" -z relro --hash-style=gnu --eh-frame-hdr -m elf_x86_64 -dynamic-linker /lib64/ld-linux-x86-64.so.2 -o a.out...

On 3 Apr 2013, at 18:42, Sean Silva <silvas at purdue.edu> wrote: > I'm not sure how difficult it actually is to follow ToT compared to one huge pain when upgrading for our full releases. I think it would be valuable to obtain feedback from projects that rely on LLVM as to how they go about integrating LLVM into their project and how our releases (and potentially dot-releases) would

Hey Jingyue, Though I tried `opt -nvvm-reflect` on both bc files, the nvvm reflect anchor didn't go away; ptxas is still complaining about the duplicate definition of of function '_ZL21__nvvm_reflect_anchorv' . Did I misused the nvvm-reflect pass? Thanks! yuanfeng On Fri, Mar 11, 2016 at 10:10 AM, Jingyue Wu <jingyue at google.com> wrote: > According to the examples you