similar to: [LLVMdev] MIPS & GP register

On Aug 15, 2012, at 11:56 PM, Eli Friedman wrote: > On Wed, Aug 15, 2012 at 10:17 PM, Carl Norum <carl at lytro.com> wrote: >>> -march=mips32r2 >>> -mtune=4kem >>> -msoft-float >>> -EL >>> >>> -Xclang -triple -Xclang mipsel-sde-elf >>> -Xclang -mrelocation-model -Xclang static >>> >>>

On Wed, Aug 15, 2012 at 10:17 PM, Carl Norum <carl at lytro.com> wrote: >> -march=mips32r2 >> -mtune=4kem >> -msoft-float >> -EL >> >> -Xclang -triple -Xclang mipsel-sde-elf >> -Xclang -mrelocation-model -Xclang static >> >> -Xclang -mllvm -Xclang -mips-ssection-threshold=0 >> -Xclang -mllvm -Xclang

On Thu, Aug 16, 2012 at 10:37 AM, Carl Norum <carl at lytro.com> wrote: > > On Aug 15, 2012, at 11:56 PM, Eli Friedman wrote: > >> On Wed, Aug 15, 2012 at 10:17 PM, Carl Norum <carl at lytro.com> wrote: >>>> -march=mips32r2 >>>> -mtune=4kem >>>> -msoft-float >>>> -EL >>>> >>>> -Xclang

(forwarding to llvm-dev) ---------- Forwarded message ---------- From: Akira Hatanaka <ahatanak at gmail.com> Date: Fri, Aug 17, 2012 at 2:35 PM Subject: Re: [LLVMdev] MIPS & GP register To: Carl Norum <carl at lytro.com> Will something like this fix the problem? if (!Subtarget.isLinux()) { reserve GP and GP_64 } To improve code, we have stopped reserving GP as a dedicated

On Aug 17, 2012, at 2:36 PM, Akira Hatanaka wrote: > (forwarding to llvm-dev) > > ---------- Forwarded message ---------- > From: Akira Hatanaka <ahatanak at gmail.com> > Date: Fri, Aug 17, 2012 at 2:35 PM > Subject: Re: [LLVMdev] MIPS & GP register > To: Carl Norum <carl at lytro.com> > > > Will something like this fix the problem? > > if

On Aug 16, 2012, at 10:58 AM, Eli Friedman wrote: > That's weird... you're probably triggering some sort of bad case in > the driver logic which tries to call gcc to assemble and link on > targets where we don't know what to do. That logic is generally a bit > shaky to begin with. It sounds like that means "time to file a bug". =) Which product should I file

Hello, I am getting the following error while trying to build a benchmark with a custom function pass: clang -Xclang -fopenmp=libomp -Xclang -load -Xclang my_lib.so file.c error: unknown argument: '-fopenmp=libomp' If I use this instead: clang -Xclang -fopenmp=libomp -Xclang -load -Xclang my_lib.so file.c I get the error: fatal error: 'omp.h' file not found I am not

On 01/16/2012 03:37 PM, Pieter Custers wrote: > Hello Tobi, > > Thank you for the quick reply. > > I updated my complete build suite with your script (http://polly.grosser.es/polly.sh). The make-test fails with some errors, the rest went smoothly; > > -- > Exit Code: 1 > Command Output (stderr): > -- > LLVM ERROR: Could not resolve external global address: stdout

Not really. Clang does not have a way to annotate device vs. kernel functions in C/C++ mode. You're probably better off trying to use OpenCL or CUDA mode in clang. In the clang unit tests, there is a cuda.h header that provides very basic support for these keywords: tests/SemaCUDA/cuda.h If you compile as CUDA (use .cu extension, or "-x cuda") and use this header, you will have

-disable-O0-optnone has no effect with anything other than -O0. -O0 being passed to clang also causes all functions to be marked noinline. I don't know if there is a command line option to turn that off. I recommend passing "-O1 -Xclang -disable-llvm-passes" to clang. Passing -O0 very specifically means disable optimizations. ~Craig On Sat, Jan 6, 2018 at 12:25 PM, toddy wang

Well, I tried the command line given by you and I get the following error clang++ nbody.kernel.cu -Xclang -fcuda-is-device -I/home/upitamba/llvm-3.2.src/tools/clang/test/SemaCUDA/ -Xclang -triple -Xclang nvptx64 -Xclang -target-cpu -Xclang sm_10 -S fatal error: error in backend: Cannot select: 0x334a870: v4f32 = NVPTXISD::MoveParam 0x334a770 [ORD=1] [ID=22] 0x334a770: v4f32 =

@Craig and @Michael After installing clang-5.0 (download from http://releases.llvm.org, does not have Flang build's slowdown mention above), 1. clang++ -O0 -Xclang -disable-O0-optnone -Xclang -disable-llvm-passes -c -emit-llvm -o a.bc LULESH.cc; opt -O3 a.bc -o b.bc; llc -O3 -filetype=obj b.bc -o b.o ; clang++ b.o -o b.out; ./b.out 20 runtime: 2.354069e+01 2. clang++ -O1 -Xclang

Why are you using build directions from "flang" which is a fortran compiler and maintained by different people than the LLVM/clang community? But then compiling C/C++ code? Their bug database should be used for filing bugs against the fortran compiler not a C/C++ compiler issue. ~Craig On Sat, Jan 6, 2018 at 1:04 PM, toddy wang <wenwangtoddy at gmail.com> wrote: > Thanks a

Thanks a lot, it is clear to me now. BTW, for Clang's slowdown, I submit an issue here: https://github.com/flang-compiler/flang/issues/356 I have no idea about the root cause. Maybe due to debug symbols. But, I already use -DCMAKE_BUILD_TYPE=Release. Anyway, I believe there is a bug somewhere. On Sat, Jan 6, 2018 at 3:43 PM, Craig Topper <craig.topper at gmail.com> wrote: >

Hello, I m trying to test individual O3 optimizations/ replicating O3 behavior on IR. I took unoptimized IR (O0), used disable-o0-optnone via (*clang -O0 -Xclang -disable-O0-optnone*). I read somewhere about *clang -O1 -Xclang -disable-O0-optnone,* so I also tested on this initial IR. I have observed by using individual optimizations, the performance (i.e time) is better when the base/initial

On 10/07/2011 03:43 PM, Marcello Maggioni wrote: > 2011/10/7 Marcello Maggioni<hayarms at gmail.com>: >> Hi, >> >> for example this loop: >> >> #include<stdio.h> >> >> int main() >> { >> int A[1024]; >> int j, k=10; >> for (j = 1; j< 1024; j++) >> A[j] =

That particular error is fixed in trunk, but with your code I'm now hitting a new issue. I'll get the fix in soon. On Fri, Mar 22, 2013 at 1:08 AM, upit <uday_pitambare at yahoo.com> wrote: > Well, I tried the command line given by you and I get the following error > > clang++ nbody.kernel.cu -Xclang -fcuda-is-device >

Hi All, We trying to use clang+llvm to generate the gcc coverage format as clang version 3.6.0 $clang --coverage -Xclang -coverage-cfg-checksum -Xclang -coverage-no-function-names-in-data -Xclang -coverage-version='407*' test.c $a.out $llvm-cov gcov test.gcda Unexpected version: *704. Invalid .gcno File! Debugging the above cause ,But any hints from experts here ,will help a lot

Hi Justin , Thank you for the confirmation and we would like to know that ,going forward the clang has the support the gcc gcov format or use the -fprofile-instr-generate -fcoverage-mapping and get ride of gcov format . We are planing to customize the clang code coverage for embedded world ,before we start tweaking the gcov / -fprofile-instr-generate code-base ,we would like to take feedback

@Zhaopei, thanks for the clarification. @Craig and @Michael, for clang 4.0.1, -Xclang -disable-O0-optnone gives the following error message. From which version -disable-O0-optnone gets supported? [twang15 at c89 temp]$ clang++ -O0 -Xclang -disable-O0-optnone -Xclang -disable-llvm-passes -c -emit-llvm -o a.bc LULESH.cc error: unknown argument: '-disable-O0-optnone' [twang15 at c89