Re: [PATCH] Fix source locations of bad enum values (PR c/71610 and PR c/71613)

2016-07-20 Thread David Malcolm
On Wed, 2016-07-20 at 16:16 -0400, Jason Merrill wrote: > On Thu, Jun 30, 2016 at 1:49 PM, Jason Merrill > wrote: > > This needs a template testcase. > > Did you get this reply before? It bounced from the mailing list, but > I thought you would have gotten it directly. I did;

Re: [PATCH] Fix source locations of bad enum values (PR c/71610 and PR c/71613)

2016-07-20 Thread Jason Merrill
On Thu, Jun 30, 2016 at 1:49 PM, Jason Merrill wrote: > This needs a template testcase. Did you get this reply before? It bounced from the mailing list, but I thought you would have gotten it directly. Jason

Re: [PATCH] Fix source locations of bad enum values (PR c/71610 and PR c/71613)

2016-07-20 Thread Jeff Law
On 06/22/2016 08:52 PM, David Malcolm wrote: PR c/71613 identifies a problem where we fail to report this enum: enum { e1 = LLONG_MIN }; with -pedantic, due to LLONG_MIN being inside a system header. This patch updates the C and C++ frontends to use the location of the name as the primary

Re: [PATCH] Fix source locations of bad enum values (PR c/71610 and PR c/71613)

2016-06-29 Thread Joseph Myers
On Wed, 22 Jun 2016, David Malcolm wrote: > PR c/71613 identifies a problem where we fail to report this enum: > > enum { e1 = LLONG_MIN }; > > with -pedantic, due to LLONG_MIN being inside a system header. > > This patch updates the C and C++ frontends to use the location of the > name as

[PATCH] Fix source locations of bad enum values (PR c/71610 and PR c/71613)

2016-06-22 Thread David Malcolm
PR c/71613 identifies a problem where we fail to report this enum: enum { e1 = LLONG_MIN }; with -pedantic, due to LLONG_MIN being inside a system header. This patch updates the C and C++ frontends to use the location of the name as the primary location in the diagnostic, supplying the