<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">On 13-08-28 02:50 PM, Eli Friedman
wrote:<br>
</div>
<blockquote
cite="mid:CAJdarcFcz6W6MfvAGv+qo58kojK_gMEPd=ej6A5o6zE9kNri7A@mail.gmail.com"
type="cite">
<div dir="ltr">On Wed, Aug 28, 2013 at 11:08 AM, Halfdan
Ingvarsson <span dir="ltr"><<a moz-do-not-send="true"
href="mailto:halfdan@sidefx.com" target="_blank">halfdan@sidefx.com</a>></span>
wrote:<br>
<div class="gmail_extra">
<div class="gmail_quote">
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div text="#000000" bgcolor="#FFFFFF">
<div class="im"><br>
</div>
I beg to differ:<a moz-do-not-send="true"
href="http://llvm.org/pr14223" target="_blank">
http://llvm.org/pr14223</a><br>
<br>
We still have to compile the affected project with -O1
to ensure that the destructors properly fire.<br>
</div>
<div text="#000000" bgcolor="#FFFFFF"><br>
</div>
</blockquote>
<div><br>
</div>
<div>I know the compiler has lots of bugs; I work on them
every day. :) It's still not the first explanation to
look for.</div>
<br>
</div>
</div>
</div>
</blockquote>
And for that I salute you. I wish I had more time to investigate
that one particular issue. The trappings of modern life, and all
that :)<br>
<br>
That said, I do tend to look in the direction of the LLVM optimizer
when gcc debug/optimized & clang debug all give the same answer,
but clang optimized disagrees. <br>
<br>
When faced with an optimizer bug, it would be great to be able to
quickly narrow down a particular function (or set of) with an
attribute, rather than extract potential culprits into their own
source with its own optimization level. This is especially true in
the presence of large code bases with hairy build systems, helper
classes internal to compile-units, and myriad static helper
functions. I do this sometimes with gcc, especially because we build
our product for multiple gcc versions. That way we can just disable
specific optimizations for a given gcc version with a known
optimizer bug. It's not ideal but it gets the job done.<br>
<br>
I know this feature is already being discussed, I'm just throwing my
vote in that direction.<br>
<br>
- ½<br>
<br>
</body>
</html>