[llvm-dev] LTO prevention help

[Jon Slenk via llvm-dev]

hi,

Thank you for your thoughtful message and for taking the time. I apologize
for not making a better example. The actual repro case I have is more
complex; I was trying to show a more succinct example but I have failed to
make it be a reproducing one. Mea culpa.

Your reply has I think led me to a small epiphany. I had though the code
was elided, but I think I now see that it is instead re-ordered.
Empirically I am seeing that the 2 breakpoints I have are happening A-B
w/out LTO but B-A with LTO.

So I am reading up on that e.g.
http://stackoverflow.com/questions/11106875/attribute-constructor-call-order-confusion

sincerely.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20161013/e977a40b/attachment.html>