On 03/17/2016 06:40 PM, Martin Sebor wrote:
On 03/17/2016 08:07 AM, Jason Merrill wrote:
On 03/09/2016 05:09 PM, Martin Sebor wrote:
While going through constexpr bugs looking for background
on one I'm currently working on I came across bug 65579 -
[C++11] gcc requires definition of a static co
On 03/17/2016 08:07 AM, Jason Merrill wrote:
On 03/09/2016 05:09 PM, Martin Sebor wrote:
While going through constexpr bugs looking for background
on one I'm currently working on I came across bug 65579 -
[C++11] gcc requires definition of a static constexpr member
even though it is not odr-used
On 03/09/2016 05:09 PM, Martin Sebor wrote:
While going through constexpr bugs looking for background
on one I'm currently working on I came across bug 65579 -
[C++11] gcc requires definition of a static constexpr member
even though it is not odr-used.
The bug points out that GCC (sometimes) emi
I'm looking for a review of the patch below. The problem isn't
new (it has existed since at least 4.9) but the fix seems trivial
and safe. If it isn't appropriate at this stage please let me
know and I'll resubmit it when stage 1 opens.
https://gcc.gnu.org/ml/gcc-patches/2016-03/msg00593.html
While going through constexpr bugs looking for background
on one I'm currently working on I came across bug 65579 -
[C++11] gcc requires definition of a static constexpr member
even though it is not odr-used.
The bug points out that GCC (sometimes) emits references to
static constexpr data member
