search for: precodegen

...save-temps " to generate the makefile and to make the whole program. However, found four different kinds of bitcode for each target. For example, I am compiling coreutils. For the program "nohup", I can get nohup.0.0.preopt.bc nohup.0.2.internalize.bc nohup.0.4.opt.bc nohup.0.5.precodegen.bc If I am right, I can also get the bitcode with emit-llvm option in clang. May I know which bc among the above four should be the same as the one I generated with emit-llvm. More information are very thankful. Regards Muhui -------------- next part -------------- An HTML attachment was scrubbed...

Hi Muhui, I tried to grep the "DW_TAG_subprogram" from the debug_info . However, I noticed that the number I found is still less than the whole functions I found with LLVM IR. Do you have any experiences? Many Thanks The only explanation that comes to mind, is that the functions are not in the final binary object file. However, previously you said you believed they were present. If

...merges the IR for all files being linked and optimizes them as a single monolithic module. The preopt.bc is the merged IR just after merging and before performing any LTO optimizations. internalize.bc is after performing whole program internalization. opt.bc is after the optimization pipeline, and .precodegen.bc is immediately before native code generation. The emit-llvm option will give you the IR for a single source file when you compile it with -c. All of those files when combined give the IR in the preopt.bc temp file. Hope that helps, Teresa On Tue, May 15, 2018 at 4:43 AM Muhui Jiang via llvm-d...

To compile an auto-tooled project to bitcode, I used to use plugin-opt=save-temps switch as explained in: http://gbalats.github.io/2015/12/10/compiling-autotooled-projects-to-LLVM-bitcode.html. This switch works with LLVM 3.8.0. However, it seems to have no effect with LLVM 5.0.0. I can see intermediate bitcode files on disk, but not the final one. Is the option removed altogether? Has the switch

...l files being linked and optimizes them as > a single monolithic module. The preopt.bc is the merged IR just after > merging and before performing any LTO optimizations. internalize.bc is > after performing whole program internalization. opt.bc is after the > optimization pipeline, and .precodegen.bc is immediately before native code > generation. > > The emit-llvm option will give you the IR for a single source file when > you compile it with -c. All of those files when combined give the IR in the > preopt.bc temp file. > > Hope that helps, > Teresa > > On Tue,...

..., llvm::LLVMContext & Context) Line 572 C++ The input of this testcase is huge, full repro.tar is here: (14mb) https://www.dropbox.com/s/ugv9sfqouhlszff/repro.tar?dl=0 With lld /lldsavetemps I managed to narrow down what it actually fails on, specifcally from the Island.Tests.Windows.exe.0.5.precodegen.bc (which fails too when passed to llc -O1) This is the pattern that it generates: https://gist.github.com/carlokok/fb0f1bf213ee4599d8f2442e37b23f03 If I read this correctly it somehow ends up using two compile units at once from the same type and failing because of that. I don't know if t...

...-plugin-opt=save-temps\ -flto\ -fuse-ld=gold make $ ls -gltr bash.*.bc -rw-r--r-- 1 staff 4769876 Jan 25 10:16 bash.0.0.preopt.bc -rw-r--r-- 1 staff 4769876 Jan 25 10:16 bash.0.2.internalize.bc -rw-r--r-- 1 staff 4739688 Jan 25 10:16 bash.0.4.opt.bc -rw-r--r-- 1 staff 4739688 Jan 25 10:16 bash.0.5.precodegen.bc -- Regards, Peng

...vm::LLVMContext & Context) Line 572 C++ The input of this testcase is huge, full repro.tar is here: (14mb) https://www.dropbox.com/s/ugv9sfqouhlszff/repro.tar?dl=0 With lld /lldsavetemps I managed to narrow down what it actually fails on, specifcally from the Island.Tests.Windows.exe.0.5.precodegen.bc (which fails too when passed to llc -O1) This is the pattern that it generates: https://gist.github.com/carlokok/fb0f1bf213ee4599d8f2442e37b23f03 If I read this correctly it somehow ends up using two compile units at once from the same type and failing because of that. I don't know if that...

> On macOS you just omit the '-fuse-ld=gold' and it will work out of the box. > > ./configure CC=clang RANLIB=llvm-ranlib CFLAGS=-flto > > LDFLAGS=-Wl\,-plugin-opt=save-temps\ -flto\ -fuse-ld=gold > > make No. It doesn't work on Mac OS by just omitting '-fuse-ld=gold'. $ ../../../extract/bash-5.0/configure CC=clang CXX=clang++ RANLIB=llvm-ranlib

Hi, I wanted to get the linked result in LLVM bitcode format. With LTO, this can be done by -flto -Wl,-plugin-opt,emit-llvm. Instead of generating native executables, it outputs a file with bitcode format. Does this still work with -flto=thin? -flto=thin -Wl,-plugin-opt,emit-llvm outputs a bitcode file, but its file size is too small, and does not contain all contents. What is the correct way

We are going to be at the llvm-dev meeting the next two days. We will get back to you after that. Sri On Mon, Oct 21, 2019 at 10:07 PM Maksim Panchenko <maks at fb.com> wrote: > Hi Sri, > > > > Thank you for replying to our feedback. 7 out 12 high-level concerns have > been > > answered; 2 of them are fully addressed. The rest are being tracked at the > >