Displaying 3 results from an estimated 3 matches for "7aaf6025".
2013 Nov 26
2
[LLVMdev] Disabling certain optimizations at -O1?
...gt; debugging, though.
>
So, do we have two ways of running SimplifyCFG? One for O1 and one for O2+,
and selectively disabling parts of it?
--renato
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20131126/7aaf6025/attachment.html>
2013 Nov 26
0
[LLVMdev] Disabling certain optimizations at -O1?
I'd support disabling tail merging of calls at -O1. The other CFG
simplification doesn't seem like that big of a deal though for general
debugging, though.
On Tue, Nov 26, 2013 at 3:57 AM, Evgeniy Stepanov <eugeni.stepanov at gmail.com
> wrote:
> Hi,
>
> there are optimizations, mostly dealing with hoisting/merging common
> code including function calls, that breaks
2013 Nov 26
5
[LLVMdev] Disabling certain optimizations at -O1?
Hi,
there are optimizations, mostly dealing with hoisting/merging common
code including function calls, that breaks stack trace symbolization
in a very bad way.
int f(int x) {
if (x == 1)
report("a");
else if (x == 2)
report("b");
return 0;
}
For example, in the above function (at -O1) both calls to report() are
done from the same PC. As a result, stack trace