search for: thinltobitcodewriterpass

..."opt -module-summary=". However, some time ago >>>>>> when Peter added the support for splitting the bitcode (for CFI purposes) >>>>>> and therefore needed to generate a summary in each partition (Thin and >>>>>> Regular), he added the ThinLTOBitcodeWriterPass, which invokes the module >>>>>> summary builder directly (twice). This writer is what gets invoked now when >>>>>> building via "clang -flto=thin", and with "opt -thinlto-bc". So there it is >>>>>> not invoked/maintained as...

...invoked by "opt -module-summary=". However, some time ago >>>>> when Peter added the support for splitting the bitcode (for CFI purposes) >>>>> and therefore needed to generate a summary in each partition (Thin and >>>>> Regular), he added the ThinLTOBitcodeWriterPass, which invokes the module >>>>> summary builder directly (twice). This writer is what gets invoked now when >>>>> building via "clang -flto=thin", and with "opt -thinlto-bc". So there it is >>>>> not invoked/maintained as an analysis...

..."opt -module-summary=". However, some time ago >>>>>> when Peter added the support for splitting the bitcode (for CFI purposes) >>>>>> and therefore needed to generate a summary in each partition (Thin and >>>>>> Regular), he added the ThinLTOBitcodeWriterPass, which invokes the module >>>>>> summary builder directly (twice). This writer is what gets invoked now when >>>>>> building via "clang -flto=thin", and with "opt -thinlto-bc". So there it is >>>>>> not invoked/maintained as...

...odule-summary=". However, some time ago >>>>>>> when Peter added the support for splitting the bitcode (for CFI purposes) >>>>>>> and therefore needed to generate a summary in each partition (Thin and >>>>>>> Regular), he added the ThinLTOBitcodeWriterPass, which invokes the module >>>>>>> summary builder directly (twice). This writer is what gets invoked now when >>>>>>> building via "clang -flto=thin", and with "opt -thinlto-bc". So there it is >>>>>>> not invoked/ma...

...an analysis pass. >> I.e. when invoked by "opt -module-summary=". However, some time ago when >> Peter added the support for splitting the bitcode (for CFI purposes) and >> therefore needed to generate a summary in each partition (Thin and >> Regular), he added the ThinLTOBitcodeWriterPass, which invokes the module >> summary builder directly (twice). This writer is what gets invoked now when >> building via "clang -flto=thin", and with "opt -thinlto-bc". So there it is >> not invoked/maintained as an analysis pass/result. It would be tricky to &...

...odule-summary=". However, some time ago >>>>>>> when Peter added the support for splitting the bitcode (for CFI purposes) >>>>>>> and therefore needed to generate a summary in each partition (Thin and >>>>>>> Regular), he added the ThinLTOBitcodeWriterPass, which invokes the module >>>>>>> summary builder directly (twice). This writer is what gets invoked now when >>>>>>> building via "clang -flto=thin", and with "opt -thinlto-bc". So there it is >>>>>>> not invoked/ma...

...invoked by "opt -module-summary=". However, some time ago >>>>> when Peter added the support for splitting the bitcode (for CFI purposes) >>>>> and therefore needed to generate a summary in each partition (Thin and >>>>> Regular), he added the ThinLTOBitcodeWriterPass, which invokes the module >>>>> summary builder directly (twice). This writer is what gets invoked now when >>>>> building via "clang -flto=thin", and with "opt -thinlto-bc". So there it is >>>>> not invoked/maintained as an analysis...

...s. I.e. when invoked by "opt -module-summary=". However, some time ago >>>> when Peter added the support for splitting the bitcode (for CFI purposes) >>>> and therefore needed to generate a summary in each partition (Thin and >>>> Regular), he added the ThinLTOBitcodeWriterPass, which invokes the module >>>> summary builder directly (twice). This writer is what gets invoked now when >>>> building via "clang -flto=thin", and with "opt -thinlto-bc". So there it is >>>> not invoked/maintained as an analysis pass/result....

...ary analysis is an analysis pass. > I.e. when invoked by "opt -module-summary=". However, some time ago when > Peter added the support for splitting the bitcode (for CFI purposes) and > therefore needed to generate a summary in each partition (Thin and > Regular), he added the ThinLTOBitcodeWriterPass, which invokes the module > summary builder directly (twice). This writer is what gets invoked now when > building via "clang -flto=thin", and with "opt -thinlto-bc". So there it is > not invoked/maintained as an analysis pass/result. It would be tricky to > figure o...

..."opt -module-summary=". However, some time ago >>>>>> when Peter added the support for splitting the bitcode (for CFI purposes) >>>>>> and therefore needed to generate a summary in each partition (Thin and >>>>>> Regular), he added the ThinLTOBitcodeWriterPass, which invokes the module >>>>>> summary builder directly (twice). This writer is what gets invoked now when >>>>>> building via "clang -flto=thin", and with "opt -thinlto-bc". So there it is >>>>>> not invoked/maintained as...

...invoked by "opt -module-summary=". However, some time ago >>>>> when Peter added the support for splitting the bitcode (for CFI purposes) >>>>> and therefore needed to generate a summary in each partition (Thin and >>>>> Regular), he added the ThinLTOBitcodeWriterPass, which invokes the module >>>>> summary builder directly (twice). This writer is what gets invoked now when >>>>> building via "clang -flto=thin", and with "opt -thinlto-bc". So there it is >>>>> not invoked/maintained as an analysis...

..."opt -module-summary=". However, some time ago >>>>>> when Peter added the support for splitting the bitcode (for CFI purposes) >>>>>> and therefore needed to generate a summary in each partition (Thin and >>>>>> Regular), he added the ThinLTOBitcodeWriterPass, which invokes the module >>>>>> summary builder directly (twice). This writer is what gets invoked now when >>>>>> building via "clang -flto=thin", and with "opt -thinlto-bc". So there it is >>>>>> not invoked/maintained as...

.... >>> I.e. when invoked by "opt -module-summary=". However, some time ago when >>> Peter added the support for splitting the bitcode (for CFI purposes) and >>> therefore needed to generate a summary in each partition (Thin and >>> Regular), he added the ThinLTOBitcodeWriterPass, which invokes the module >>> summary builder directly (twice). This writer is what gets invoked now when >>> building via "clang -flto=thin", and with "opt -thinlto-bc". So there it is >>> not invoked/maintained as an analysis pass/result. It would be...

...ases the module summary analysis is an analysis pass. I.e. when invoked by "opt -module-summary=". However, some time ago when Peter added the support for splitting the bitcode (for CFI purposes) and therefore needed to generate a summary in each partition (Thin and Regular), he added the ThinLTOBitcodeWriterPass, which invokes the module summary builder directly (twice). This writer is what gets invoked now when building via "clang -flto=thin", and with "opt -thinlto-bc". So there it is not invoked/maintained as an analysis pass/result. It would be tricky to figure out how to even split...

...ases the module summary analysis is an analysis pass. I.e. when invoked by "opt -module-summary=". However, some time ago when Peter added the support for splitting the bitcode (for CFI purposes) and therefore needed to generate a summary in each partition (Thin and Regular), he added the ThinLTOBitcodeWriterPass, which invokes the module summary builder directly (twice). This writer is what gets invoked now when building via "clang -flto=thin", and with "opt -thinlto-bc". So there it is not invoked/maintained as an analysis pass/result. It would be tricky to figure out how to even split...

...an analysis pass. >> I.e. when invoked by "opt -module-summary=". However, some time ago when >> Peter added the support for splitting the bitcode (for CFI purposes) and >> therefore needed to generate a summary in each partition (Thin and >> Regular), he added the ThinLTOBitcodeWriterPass, which invokes the module >> summary builder directly (twice). This writer is what gets invoked now when >> building via "clang -flto=thin", and with "opt -thinlto-bc". So there it is >> not invoked/maintained as an analysis pass/result. It would be tricky to &...

...ases the module summary analysis is an analysis pass. I.e. when invoked by "opt -module-summary=". However, some time ago when Peter added the support for splitting the bitcode (for CFI purposes) and therefore needed to generate a summary in each partition (Thin and Regular), he added the ThinLTOBitcodeWriterPass, which invokes the module summary builder directly (twice). This writer is what gets invoked now when building via "clang -flto=thin", and with "opt -thinlto-bc". So there it is not invoked/maintained as an analysis pass/result. It would be tricky to figure out how to even split...

Hi, My main concern is this one: > Currently, I am emitting the summary entries at the end, after the metadata nodes. Note that the ModuleSummaryIndex is not currently referenced from the Module, and isn’t currently created when parsing the Module IR bitcode (there is a separate derived class for reading the ModuleSummaryIndex from bitcode). This is because they are not currently used at the

...ary analysis is an analysis pass. > I.e. when invoked by "opt -module-summary=". However, some time ago when > Peter added the support for splitting the bitcode (for CFI purposes) and > therefore needed to generate a summary in each partition (Thin and > Regular), he added the ThinLTOBitcodeWriterPass, which invokes the module > summary builder directly (twice). This writer is what gets invoked now when > building via "clang -flto=thin", and with "opt -thinlto-bc". So there it is > not invoked/maintained as an analysis pass/result. It would be tricky to > figure o...