It seems that the patch was tested only in the C testsuite, but the
changes to the testcase fail for C++. So I committed the following,
which is what my patch should have done in the first place, as
obvious.
I hope this is OK with you.
Cheers,
Manuel.
Index: gcc/testsuite/gcc.dg/cast-qual-3.c
=
On Tue, 11 Mar 2014, Magnus Reftel wrote:
> Currently, castring away volatile from a pointer makes -Wcast-qual
> claim that __attribute__((noreturn)) was cast away (see bugzilla
> 55383). The attached patch, originally written by Manuel L?pez-Ib??ez
> and updated to match trunk by me, correctes th
On Tue, Mar 11, 2014 at 05:10:45PM +0100, Gerald Pfeifer wrote:
> On Tue, 11 Mar 2014, Magnus Reftel wrote:
> > Currently, castring away volatile from a pointer makes -Wcast-qual
> > claim that __attribute__((noreturn)) was cast away (see bugzilla
> > 55383). The attached patch, originally written
On Tue, 11 Mar 2014, Magnus Reftel wrote:
> Currently, castring away volatile from a pointer makes -Wcast-qual
> claim that __attribute__((noreturn)) was cast away (see bugzilla
> 55383). The attached patch, originally written by Manuel López-Ibáñez
> and updated to match trunk by me, correctes tha
Currently, castring away volatile from a pointer makes -Wcast-qual
claim that __attribute__((noreturn)) was cast away (see bugzilla
55383). The attached patch, originally written by Manuel López-Ibáñez
and updated to match trunk by me, correctes that. No regressions on
gcc from applying this patch
