search for: wholeprogramdevirt

...:\llvm-project>git apply -3 patch.txt But if I switch to the release branch and try to apply: F:\llvm-project>git reset && git checkout . (...) F:\llvm-project>git checkout release/10.x (...) F:\llvm-project>git apply -3 patch.txt error: patch failed: llvm/lib/Transforms/IPO/WholeProgramDevirt.cpp:529 error: repository lacks the necessary blob to fall back on 3-way merge. error: llvm/lib/Transforms/IPO/WholeProgramDevirt.cpp: patch does not apply Is there some magic I'm not aware of? Thanks! Alex. -------------- next part -------------- An HTML attachment was scrubbed... URL: <h...

Hi, I have an analysis pass which collects information about functions based on their call sites. There are problems I'm facing with processing virtual function calls, namely . How identify virtual call sites in my pass? . How Identify candidate callees for the given virtual call site? For the following example, the information I want to get would be identify call of F and as a possible

...for merging summaries would be to link the embedded summary bitcode files into a single module using the IRMover, with a mechanism very similar to regular LTO. This would move all the necessary vtables and metadata into a single module where they can be processed using the existing LowerBitSets and WholeProgramDevirt passes, which would be extended to export summary metadata. This summary metadata would be copied into the regular summary information, where it can be used by individual ThinLTO backends. In the future, we could also consider representing importing summaries as metadata. That would also make the...

...hich is >>> optionally emitted as a bitcode file.Currently, the only way to view these >>> records is via “llvm-bcanalyzer -dump”, then manually decoding the raw >>> bitcode dumps.Relatedly, there is YAML reader/writer support for CFI >>> related summary fields (-wholeprogramdevirt-read-summary and >>> -wholeprogramdevirt-write-summary). Last summer, GSOC student Charles >>> Saternos implemented support to dump the summary in YAML from llvm-lto2 >>> (D34080), including the rest of the summary fields (D34063), however, there >>> was pushback...

...the Thin Link, which is >> optionally emitted as a bitcode file.Currently, the only way to view these >> records is via “llvm-bcanalyzer -dump”, then manually decoding the raw >> bitcode dumps.Relatedly, there is YAML reader/writer support for CFI >> related summary fields (-wholeprogramdevirt-read-summary and >> -wholeprogramdevirt-write-summary). Last summer, GSOC student Charles >> Saternos implemented support to dump the summary in YAML from llvm-lto2 >> (D34080), including the rest of the summary fields (D34063), however, there >> was pushback on the related...

...>> optionally emitted as a bitcode file.Currently, the only way to view these >>>> records is via “llvm-bcanalyzer -dump”, then manually decoding the raw >>>> bitcode dumps.Relatedly, there is YAML reader/writer support for CFI >>>> related summary fields (-wholeprogramdevirt-read-summary and >>>> -wholeprogramdevirt-write-summary). Last summer, GSOC student Charles >>>> Saternos implemented support to dump the summary in YAML from llvm-lto2 >>>> (D34080), including the rest of the summary fields (D34063), however, there >>>&...

...ionally emitted as a bitcode file.Currently, the only way to view these >>>>> records is via “llvm-bcanalyzer -dump”, then manually decoding the raw >>>>> bitcode dumps.Relatedly, there is YAML reader/writer support for CFI >>>>> related summary fields (-wholeprogramdevirt-read-summary and >>>>> -wholeprogramdevirt-write-summary). Last summer, GSOC student Charles >>>>> Saternos implemented support to dump the summary in YAML from llvm-lto2 >>>>> (D34080), including the rest of the summary fields (D34063), however, there &...

...g all the per-module indexes during the Thin Link, which is optionally emitted as a bitcode file.Currently, the only way to view these records is via “llvm-bcanalyzer -dump”, then manually decoding the raw bitcode dumps.Relatedly, there is YAML reader/writer support for CFI related summary fields (-wholeprogramdevirt-read-summary and -wholeprogramdevirt-write-summary). Last summer, GSOC student Charles Saternos implemented support to dump the summary in YAML from llvm-lto2 (D34080), including the rest of the summary fields (D34063), however, there was pushback on the related RFC for dumping via YAML or another...

...the Thin Link, which is >> optionally emitted as a bitcode file.Currently, the only way to view these >> records is via “llvm-bcanalyzer -dump”, then manually decoding the raw >> bitcode dumps.Relatedly, there is YAML reader/writer support for CFI >> related summary fields (-wholeprogramdevirt-read-summary and >> -wholeprogramdevirt-write-summary). Last summer, GSOC student Charles >> Saternos implemented support to dump the summary in YAML from llvm-lto2 >> (D34080), including the rest of the summary fields (D34063), however, there >> was pushback on the related...

...indexes during the Thin Link, which is > optionally emitted as a bitcode file.Currently, the only way to view these > records is via “llvm-bcanalyzer -dump”, then manually decoding the raw > bitcode dumps.Relatedly, there is YAML reader/writer support for CFI > related summary fields (-wholeprogramdevirt-read-summary and > -wholeprogramdevirt-write-summary). Last summer, GSOC student Charles > Saternos implemented support to dump the summary in YAML from llvm-lto2 > (D34080), including the rest of the summary fields (D34063), however, there > was pushback on the related RFC for dumping...

...hich is >>> optionally emitted as a bitcode file.Currently, the only way to view these >>> records is via “llvm-bcanalyzer -dump”, then manually decoding the raw >>> bitcode dumps.Relatedly, there is YAML reader/writer support for CFI >>> related summary fields (-wholeprogramdevirt-read-summary and >>> -wholeprogramdevirt-write-summary). Last summer, GSOC student Charles >>> Saternos implemented support to dump the summary in YAML from llvm-lto2 >>> (D34080), including the rest of the summary fields (D34063), however, there >>> was pushback...

...ted as a bitcode file.Currently, the only way to view these >>>>>> records is via “llvm-bcanalyzer -dump”, then manually decoding the raw >>>>>> bitcode dumps.Relatedly, there is YAML reader/writer support for CFI >>>>>> related summary fields (-wholeprogramdevirt-read-summary and >>>>>> -wholeprogramdevirt-write-summary). Last summer, GSOC student Charles >>>>>> Saternos implemented support to dump the summary in YAML from llvm-lto2 >>>>>> (D34080), including the rest of the summary fields (D34063), howe...

...>> optionally emitted as a bitcode file.Currently, the only way to view these >>>> records is via “llvm-bcanalyzer -dump”, then manually decoding the raw >>>> bitcode dumps.Relatedly, there is YAML reader/writer support for CFI >>>> related summary fields (-wholeprogramdevirt-read-summary and >>>> -wholeprogramdevirt-write-summary). Last summer, GSOC student Charles >>>> Saternos implemented support to dump the summary in YAML from llvm-lto2 >>>> (D34080), including the rest of the summary fields (D34063), however, there >>>&...

...indexes during the Thin Link, which is > optionally emitted as a bitcode file.Currently, the only way to view these > records is via “llvm-bcanalyzer -dump”, then manually decoding the raw > bitcode dumps.Relatedly, there is YAML reader/writer support for CFI > related summary fields (-wholeprogramdevirt-read-summary and > -wholeprogramdevirt-write-summary). Last summer, GSOC student Charles > Saternos implemented support to dump the summary in YAML from llvm-lto2 > (D34080), including the rest of the summary fields (D34063), however, there > was pushback on the related RFC for dumping...

...code file.Currently, the only way to view these >>>>>>> records is via “llvm-bcanalyzer -dump”, then manually decoding the raw >>>>>>> bitcode dumps.Relatedly, there is YAML reader/writer support for CFI >>>>>>> related summary fields (-wholeprogramdevirt-read-summary and >>>>>>> -wholeprogramdevirt-write-summary). Last summer, GSOC student Charles >>>>>>> Saternos implemented support to dump the summary in YAML from llvm-lto2 >>>>>>> (D34080), including the rest of the summary fields (D...

...exes during the Thin Link, which is optionally emitted as a bitcode file. > > Currently, the only way to view these records is via “llvm-bcanalyzer -dump”, then manually decoding the raw bitcode dumps. > > Relatedly, there is YAML reader/writer support for CFI related summary fields (-wholeprogramdevirt-read-summary and -wholeprogramdevirt-write-summary). Last summer, GSOC student Charles Saternos implemented support to dump the summary in YAML from llvm-lto2 (D34080), including the rest of the summary fields (D34063), however, there was pushback on the related RFC for dumping via YAML or another...

...only way to view these >>>>>>>>> records is via “llvm-bcanalyzer -dump”, then manually decoding the raw >>>>>>>>> bitcode dumps.Relatedly, there is YAML reader/writer support for CFI >>>>>>>>> related summary fields (-wholeprogramdevirt-read-summary and >>>>>>>>> -wholeprogramdevirt-write-summary). Last summer, GSOC student Charles >>>>>>>>> Saternos implemented support to dump the summary in YAML from llvm-lto2 >>>>>>>>> (D34080), including the rest...

...indexes during the Thin Link, which is > optionally emitted as a bitcode file.Currently, the only way to view these > records is via “llvm-bcanalyzer -dump”, then manually decoding the raw > bitcode dumps.Relatedly, there is YAML reader/writer support for CFI > related summary fields (-wholeprogramdevirt-read-summary and > -wholeprogramdevirt-write-summary). Last summer, GSOC student Charles > Saternos implemented support to dump the summary in YAML from llvm-lto2 > (D34080), including the rest of the summary fields (D34063), however, there > was pushback on the related RFC for dumping...

...rrently, the only way to view these >>>>>>>> records is via “llvm-bcanalyzer -dump”, then manually decoding the raw >>>>>>>> bitcode dumps.Relatedly, there is YAML reader/writer support for CFI >>>>>>>> related summary fields (-wholeprogramdevirt-read-summary and >>>>>>>> -wholeprogramdevirt-write-summary). Last summer, GSOC student Charles >>>>>>>> Saternos implemented support to dump the summary in YAML from llvm-lto2 >>>>>>>> (D34080), including the rest of the summa...

...nterestingly, running the pass later seems to help with performance as well. Though the comment in PassManagerBuilder implies that this pass needs to run early. Why is it different from full LTO? > > The issue with running the passes early is that the llvm.assume(llvm.type.test) pattern that WholeProgramDevirt looks for is somewhat fragile, so it needs to see the IR first before one of the other passes can break it. (This is probably something that we want to fix by using a different pattern.) I don't think that the same issue exists with any of the patterns that LowerTypeTests looks for, so it would...