search for: modulesummaryindex

...he summaries are emitted as LLVM Bitcode, however, not currently in the LLVM assembly.There are two ways to generate a bitcode file containing summary records for a module: 1. Compile with “clang -c -flto=thin”2. Build from LLVM assembly using “opt -module-summary”Either of these will result in the ModuleSummaryIndex analysis pass (which builds the summary index in memory for a module) to be added to the pipeline just before bitcode emission.Additionally, a combined index is created by merging all the per-module indexes during the Thin Link, which is optionally emitted as a bitcode file.Currently, the only way...

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 same time. However, in the future there is no reason wh...

...> Teresa > > On Tue, May 1, 2018 at 11:37 AM, Mehdi AMINI <joker.eph at gmail.com> wrote: > >> 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 same time. However,...

Hey all, I'm working on adding function attribute propagation to function summaries in the ThinLTO index, and have run into some trouble with ensuring bottom-up traversal when finding the SCCs in the call graph. I'm basing my implementation for the GraphTraits for the ModuleSummaryIndex off the GraphTraits<CallGraph *> implementation ( http://llvm-cs.pcc.me.uk/include/llvm/Analysis/CallGraph.h#407). In the GraphTrait<CallGraph *> definition, the getEntryNode function returns the external calling node ( http://llvm-cs.pcc.me.uk/include/llvm/Analysis/CallGraph.h#450), wh...

...code, however, not currently >> in the LLVM assembly.There are two ways to generate a bitcode file >> containing summary records for a module: 1. Compile with “clang -c >> -flto=thin”2. Build from LLVM assembly using “opt -module-summary”Either of >> these will result in the ModuleSummaryIndex analysis pass (which builds the >> summary index in memory for a module) to be added to the pipeline just >> before bitcode emission.Additionally, a combined index is created by >> merging all the per-module indexes during the Thin Link, which is >> optionally emitted as a b...

...s, responses and a tweaked proposal below. Teresa On Tue, May 1, 2018 at 11:37 AM, Mehdi AMINI <joker.eph at gmail.com> wrote: > 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 same time. However, in the future t...

...tted as LLVM Bitcode, however, not currently > in the LLVM assembly.There are two ways to generate a bitcode file > containing summary records for a module: 1. Compile with “clang -c > -flto=thin”2. Build from LLVM assembly using “opt -module-summary”Either of > these will result in the ModuleSummaryIndex analysis pass (which builds the > summary index in memory for a module) to be added to the pipeline just > before bitcode emission.Additionally, a combined index is created by > merging all the per-module indexes during the Thin Link, which is > optionally emitted as a bitcode file.Curr...

...lt;joker.eph at gmail.com> >>> wrote: >>> >>>> 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 >>>>...

...t;>>> >>>>>> 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 cu...

...ot currently >>> in the LLVM assembly.There are two ways to generate a bitcode file >>> containing summary records for a module: 1. Compile with “clang -c >>> -flto=thin”2. Build from LLVM assembly using “opt -module-summary”Either of >>> these will result in the ModuleSummaryIndex analysis pass (which builds the >>> summary index in memory for a module) to be added to the pipeline just >>> before bitcode emission.Additionally, a combined index is created by >>> merging all the per-module indexes during the Thin Link, which is >>> optionall...

...e, May 1, 2018 at 11:37 AM, Mehdi AMINI <joker.eph at gmail.com> wrote: >> >>> 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 sam...

...gt;>>>> 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 the...

...;>>> in the LLVM assembly.There are two ways to generate a bitcode file >>>> containing summary records for a module: 1. Compile with “clang -c >>>> -flto=thin”2. Build from LLVM assembly using “opt -module-summary”Either of >>>> these will result in the ModuleSummaryIndex analysis pass (which builds the >>>> summary index in memory for a module) to be added to the pipeline just >>>> before bitcode emission.Additionally, a combined index is created by >>>> merging all the per-module indexes during the Thin Link, which is >>&g...

...eresa > > On Tue, May 1, 2018 at 11:37 AM, Mehdi AMINI <joker.eph at gmail.com <mailto:joker.eph at gmail.com>> wrote: > 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 same time. However, in the future there is no reason wh...

...tted as LLVM Bitcode, however, not currently > in the LLVM assembly.There are two ways to generate a bitcode file > containing summary records for a module: 1. Compile with “clang -c > -flto=thin”2. Build from LLVM assembly using “opt -module-summary”Either of > these will result in the ModuleSummaryIndex analysis pass (which builds the > summary index in memory for a module) to be added to the pipeline just > before bitcode emission.Additionally, a combined index is created by > merging all the per-module indexes during the Thin Link, which is > optionally emitted as a bitcode file.Curr...

...t;>>> >>>>>> 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 cu...

...gt;>>>> 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 the...

...t;>>> >>>>>> 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 cu...

...t;>>> wrote: >>>> >>>>> 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 >...

...code, however, not currently >> in the LLVM assembly.There are two ways to generate a bitcode file >> containing summary records for a module: 1. Compile with “clang -c >> -flto=thin”2. Build from LLVM assembly using “opt -module-summary”Either of >> these will result in the ModuleSummaryIndex analysis pass (which builds the >> summary index in memory for a module) to be added to the pipeline just >> before bitcode emission.Additionally, a combined index is created by >> merging all the per-module indexes during the Thin Link, which is >> optionally emitted as a b...