Displaying 3 results from an estimated 3 matches for "d47097".
Did you mean:
47097
2018 May 31
1
[SROA][DebugInfo][GSoC] Testing SROA on amalgamated sqlite source
...r good reasons or does it look more like an oversight in the implementation?
How can I approach this? My guess is that all these phi's are with line 0 because they are made
of stores and allocas that aren't actual code, and are instead generated by clang. Like here
https://reviews.llvm.org/D47097 at test1
2018 May 30
0
[SROA][DebugInfo][GSoC] Testing SROA on amalgamated sqlite source
> On May 30, 2018, at 8:37 AM, Anast Gramm <anastasis.gramm2 at gmail.com> wrote:
>
> Introduction
> ============
>
> `SROA' is an early stage pass running at the very beginning of the
> pipeline in `-O{1,2,3}'. Greg Bedwell's report from his DExTer tool
> shows SROA on function as one of the major culprits of Debug Info
> loss.
>
> With
2018 May 30
4
[SROA][DebugInfo][GSoC] Testing SROA on amalgamated sqlite source
Introduction
============
`SROA' is an early stage pass running at the very beginning of the
pipeline in `-O{1,2,3}'. Greg Bedwell's report from his DExTer tool
shows SROA on function as one of the major culprits of Debug Info
loss.
With debugify-each partially done I tried testing this on the
amalgamated sqlite source.
The steps are as follows:
,----
| # generate