<html>
<head>
<base href="http://bugs.llvm.org/">
</head>
<body><span class="vcard"><a class="email" href="mailto:eric@efcs.ca" title="Eric Fiselier <eric@efcs.ca>"> <span class="fn">Eric Fiselier</span></a>
</span> changed
<a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED WONTFIX - Libcxx requires GNU extension when compiling with newlib"
href="http://bugs.llvm.org/show_bug.cgi?id=32479">bug 32479</a>
<br>
<table border="1" cellspacing="0" cellpadding="8">
<tr>
<th>What</th>
<th>Removed</th>
<th>Added</th>
</tr>
<tr>
<td style="text-align:right;">Status</td>
<td>NEW
</td>
<td>RESOLVED
</td>
</tr>
<tr>
<td style="text-align:right;">CC</td>
<td>
</td>
<td>eric@efcs.ca
</td>
</tr>
<tr>
<td style="text-align:right;">Resolution</td>
<td>---
</td>
<td>WONTFIX
</td>
</tr></table>
<p>
<div>
<b><a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED WONTFIX - Libcxx requires GNU extension when compiling with newlib"
href="http://bugs.llvm.org/show_bug.cgi?id=32479#c5">Comment # 5</a>
on <a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED WONTFIX - Libcxx requires GNU extension when compiling with newlib"
href="http://bugs.llvm.org/show_bug.cgi?id=32479">bug 32479</a>
from <span class="vcard"><a class="email" href="mailto:eric@efcs.ca" title="Eric Fiselier <eric@efcs.ca>"> <span class="fn">Eric Fiselier</span></a>
</span></b>
<pre><span class="quote">> I guess that's up to you guys if you want Libc++ to be POSIX compliant or
> not with newlib. Adding that macro is easy enough for our use case, but I'm
> not sure that everyone can turn GNU extensions on (especially since they are
> likely using Clang to avoid GCC). </span >
On all supported platforms Clang pre-defines `_GNU_SOURCE=1` to enable GNU
extensions by default when compiling C++. The extensions are needed to provide
a correct implementation of `locale` and input/output among other things.
Both libc++ and libstdc++ are dependent on this behavior and have been for
years. Using libc extensions allows libc++ to offer a better QoI than it could
otherwise. I don't have any motivation to try and change this. As long as libc
extensions are available libc++ should expect the compiler to enable them by
default.
<span class="quote">> It would also suggest that gnu++XXX should be used instead of std++XXX which
> seems odd for a C++ library as a requirement.</span >
I think you're confusing GLIBC extensions with GCC extensions. `-std=gnu++XX`
changes the language dialect. It should have no effect on what GLIBC offers.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are on the CC list for the bug.</li>
</ul>
</body>
</html>