<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><div>On Feb 28, 2011, at 2:07 AM, Chandler Carruth wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div class="gmail_quote">On Sun, Feb 27, 2011 at 10:57 PM, John Wiegley <span dir="ltr"><<a href="mailto:johnw@boostpro.com">johnw@boostpro.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im">On Feb 27, 2011, at 9:27 PM, Anders Carlsson wrote:<br>> Add a -fcxx-exceptions flag to the frontend, which can be used to enable<br>
> C++ exceptions, even when exceptions have been turned off using -fno-exceptions.<br>
> Make the -fobjc-exceptions flag do the same thing, but for Objective-C exceptions.<br>
<br>
</div>This change makes it so that -fexceptions no longer enables exceptions for C++.<br>
Is this intended behavior? Do C++ users really need to use -fcxx-exceptions<br>
when using clang now?<br></blockquote><div><br></div><div>The plan as I understand it is for the driver to expand '-fexceptions' into both variants as needed. I'm observing this behavior in the driver with a fresh build, so I think this should all be working. Are you observing something different?</div>
</div>
</blockquote></div><br><div>I'm seeing "exceptions are disabled" when using -fexceptions in a build as recent as about 10 minutes ago (from the Git mirrors). If there have been even more recent changes in Subversion to fix this, that's great.</div><div><br></div><div>John</div></body></html>