search for: fthinlto

...ling-else Way_.cpp clang++ -flto=thin -O3 -o thinlto.objects -Wl,-plugin-opt,thinlto-index-only=thinlto.objects CreateWay_.o Places_.o RegBounds_.o RegMng_.o Way2_.o WayInit_.o Library.o Random.o Region_.o RegWay_.o Way_.o clang++ -c -x ir CreateWay_.o -O3 -o CreateWay_-native.o -fthinlto-index=CreateWay_.o.thinlto.bc clang++ -c -x ir Places_.o -O3 -o Places_-native.o -fthinlto-index=Places_.o.thinlto.bc clang++ -c -x ir RegBounds_.o -O3 -o RegBounds_-native.o -fthinlto-index=RegBounds_.o.thinlto.bc clang++ -c -x ir RegMng_.o -O3 -o RegMng_-native.o -fthin...

...t;@" but the gnu ld manpage does). I.e. something like: clang++ -flto=thin -O3 -c -o path1/foo.o foo.cpp ... clang++ -flto=thin -O3 -Wl,-plugin-opt,thinlto-index-only=files.out -Wl,-plugin-opt,thinlto-prefix-replace=path1;path2" foo.o ... clang++ -c -x ir path1/foo.o -O3 -o path2/foo.o -fthinlto-index=path2/foo.o.thinlto.bc ... clang++ -flto=thin -O3 -o a.out @files.out But again, that should only come into play if you are linking archives of bitcode files... Teresa On Tue, Jan 8, 2019 at 2:38 PM David Callahan via llvm-dev <llvm-dev at lists.llvm.org<mailto:llvm-dev at lists.ll...

...t;@" but the gnu ld manpage does). I.e. something like: clang++ -flto=thin -O3 -c -o path1/foo.o foo.cpp ... clang++ -flto=thin -O3 -Wl,-plugin-opt,thinlto-index-only=files.out -Wl,-plugin-opt,thinlto-prefix-replace=path1;path2" foo.o ... clang++ -c -x ir path1/foo.o -O3 -o path2/foo.o -fthinlto-index=path2/foo.o.thinlto.bc ... clang++ -flto=thin -O3 -o a.out @files.out But again, that should only come into play if you are linking archives of bitcode files... Teresa On Tue, Jan 8, 2019 at 2:38 PM David Callahan via llvm-dev <llvm-dev at lists.llvm.org<mailto:llvm-dev at lists.ll...

...b.indexing.o $(clang) -fuse-ld=lld -Wl,--thinlto-index-only=a.rsp -Wl,--thinlto-prefix-replace=';lto' -Wl,--thinlto-object-suffix-replace='.indexing.o;.o' a.indexing.o b.indexing.o thinlto_backend lto/a.o lto/b.o: a.o b.o lto/a.o.thinlto.bc lto/b.o.thinlto.bc $(clang) -O2 -c -fthinlto-index=lto/a.o.thinlto.bc a.o -o lto/a.o $(clang) -O2 -c -fthinlto-index=lto/b.o.thinlto.bc b.o -o lto/b.o final_link exe: lto/a.o lto/b.o a.rsp # Propeller does basic block section reordering here. $(clang) -fuse-ld=lld @a.rsp -o exe We need to replace the two stages thinlto_backend and f...

...Xclang -fno-lto-unit -O3 -c src/lib.cpp -o src/lib.o llvm-ar -format gnu qcs lib.a lib/lib.o src/lib.o clang++ -flto=thin -o index -O3 -Wl,-plugin-opt,thinlto-index-only=thinlto.objects -Wl,-plugin-opt,thinlto-emit-imports-files main.o lib.a clang++ -c -x ir main.o -O3 -flto=thin -o main-native.o -fthinlto-index=main.o.thinlto.bc Error loading imported file 'lib.a.llvm.2596.lib.cpp': No such file or directory In this case, gold has registered the modules within my archive with ThinLTO. The string "lib.a.llvm.2596.lib.cpp" is generated with the archive in question, plus an offset in...

...TO function index/summary <http://reviews.llvm.org/D11721> D11722 [ThinLTO] Bitcode reading/writing support for ThinLTO function summary/index <http://reviews.llvm.org/D11722> D11723 [ThinLTO] ThinLTO object file interfaces <http://reviews.llvm.org/D11723> D11907 LLVM support for -fthinlto option. <http://reviews.llvm.org/D11907> D11908 Clang support for -fthinlto. <http://reviews.llvm.org/D11908> Once the basic options support, data structs, and bitcode support goes in I can send patches for generating/emitting the function index and the combined function index (off by...

...-files main.o --start-lib lib/lib.o > src/lib.o --end-lib > > things should work. > > Note you also need to do the ThinLTO backend compile for each of the > archive constituents anyway, e.g. something like: > clang++ -c -x ir lib/lib.o -O3 -flto=thin -o lib/lib-native.o > -fthinlto-index=lib/lib.o.thinlto.bc > etc > > HTH, > Teresa > > On Mon, Jun 17, 2019 at 2:46 PM Tanoy Sinha via llvm-dev < > llvm-dev at lists.llvm.org> wrote: > >> I'm trying to run distributed ThinLTO without thin archives. >> When I do, I get an error in the...

...> containing a single .llvmbc section holding the bitcode. Specifically, > > the patch would add new options “emit-llvm-bc-elf” (object file) and > > corresponding “emit-llvm-elf” (textual assembly code equivalent). > > Eventually these would be automatically triggered under “-fthinlto -c” > > and “-fthinlto -S”, respectively. > > > > Additionally, a symbol table will be generated in the ELF file, > > holding the function symbols within the bitcode. This facilitates > > handling archives of the ELF-wrapped bitcode created with $AR, since > > th...

...y generating bitcode in an ELF file containing a single .llvmbc section holding the bitcode. Specifically, the patch would add new options “emit-llvm-bc-elf” (object file) and corresponding “emit-llvm-elf” (textual assembly code equivalent). Eventually these would be automatically triggered under “-fthinlto -c” and “-fthinlto -S”, respectively. Additionally, a symbol table will be generated in the ELF file, holding the function symbols within the bitcode. This facilitates handling archives of the ELF-wrapped bitcode created with $AR, since the archive will have a symbol table as well. The archive sym...

...llvmbc section holding the bitcode. Specifically, > >> > the patch would add new options “emit-llvm-bc-elf” (object file) and > >> > corresponding “emit-llvm-elf” (textual assembly code equivalent). > >> > Eventually these would be automatically triggered under “-fthinlto -c” > >> > and “-fthinlto -S”, respectively. > >> > > >> > Additionally, a symbol table will be generated in the ELF file, > >> > holding the function symbols within the bitcode. This facilitates > >> > handling archives of the ELF-wrapped...

...gt; Specifically, > >> >> > the patch would add new options “emit-llvm-bc-elf” (object file) > and > >> >> > corresponding “emit-llvm-elf” (textual assembly code equivalent). > >> >> > Eventually these would be automatically triggered under “-fthinlto > >> >> > -c” > >> >> > and “-fthinlto -S”, respectively. > >> >> > > >> >> > Additionally, a symbol table will be generated in the ELF file, > >> >> > holding the function symbols within the bitcode. This fac...

...gt; > the patch would add new options “emit-llvm-bc-elf” (object file) >>> and >>> >> >> > corresponding “emit-llvm-elf” (textual assembly code equivalent). >>> >> >> > Eventually these would be automatically triggered under >>> “-fthinlto >>> >> >> > -c” >>> >> >> > and “-fthinlto -S”, respectively. >>> >> >> > >>> >> >> > Additionally, a symbol table will be generated in the ELF file, >>> >> >> > holding the funct...

...-llvm-bc-elf” (object file) >>> >> >> > and >>> >> >> > corresponding “emit-llvm-elf” (textual assembly code equivalent). >>> >> >> > Eventually these would be automatically triggered under >>> >> >> > “-fthinlto >>> >> >> > -c” >>> >> >> > and “-fthinlto -S”, respectively. >>> >> >> > >>> >> >> > Additionally, a symbol table will be generated in the ELF file, >>> >> >> > holding the funct...

...> >> >> > and >> >>> >> >> > corresponding “emit-llvm-elf” (textual assembly code >> equivalent). >> >>> >> >> > Eventually these would be automatically triggered under >> >>> >> >> > “-fthinlto >> >>> >> >> > -c” >> >>> >> >> > and “-fthinlto -S”, respectively. >> >>> >> >> > >> >>> >> >> > Additionally, a symbol table will be generated in the ELF >> file, >>...

...t; >> > corresponding “emit-llvm-elf” (textual assembly code >>>> >>> >> >> > equivalent). >>>> >>> >> >> > Eventually these would be automatically triggered under >>>> >>> >> >> > “-fthinlto >>>> >>> >> >> > -c” >>>> >>> >> >> > and “-fthinlto -S”, respectively. >>>> >>> >> >> > >>>> >>> >> >> > Additionally, a symbol table will be generated in...

...f we decide to go this way -- wrapping the bitcode in the native > object format -- wouldn't emit-llvm-native or emit-llvm-object be > better? The native object format is implied by the triple. Yes, that is better. > >> Eventually these would be automatically triggered under “-fthinlto -c” >> and “-fthinlto -S”, respectively. >> >> Additionally, a symbol table will be generated in the ELF file, >> holding the function symbols within the bitcode. This facilitates >> handling archives of the ELF-wrapped bitcode created with $AR, since >> the arch...

...ing “emit-llvm-elf” (textual assembly code >> >>>> >>> >> >> > equivalent). >> >>>> >>> >> >> > Eventually these would be automatically triggered under >> >>>> >>> >> >> > “-fthinlto >> >>>> >>> >> >> > -c” >> >>>> >>> >> >> > and “-fthinlto -S”, respectively. >> >>>> >>> >> >> > >> >>>> >>> >> >> > Additionally,...

...ing “emit-llvm-elf” (textual assembly code >> >>>> >>> >> >> > equivalent). >> >>>> >>> >> >> > Eventually these would be automatically triggered under >> >>>> >>> >> >> > “-fthinlto >> >>>> >>> >> >> > -c” >> >>>> >>> >> >> > and “-fthinlto -S”, respectively. >> >>>> >>> >> >> > >> >>>> >>> >> >> > Additionally,...

...tive object file containing a single .llvmbc section holding the bitcode. Specifically, the patch would add new options “emit-llvm-native-object” (object file) and corresponding “emit-llvm-native-assembly” (textual assembly code equivalent). Eventually these would be automatically triggered under “-fthinlto -c” and “-fthinlto -S”, respectively. Additionally, a symbol table will be generated in the native object file, holding the function symbols within the bitcode. This facilitates handling archives of the native object-wrapped bitcode created with $AR, since the archive will have a symbol table as...

...gt; >> >>>> >>> >> >> > equivalent). >>> >> >>>> >>> >> >> > Eventually these would be automatically triggered >>> under >>> >> >>>> >>> >> >> > “-fthinlto >>> >> >>>> >>> >> >> > -c” >>> >> >>>> >>> >> >> > and “-fthinlto -S”, respectively. >>> >> >>>> >>> >> >> > >>> >> >>>&g...