Re: [PR 95013] EOF location is at end of file

2020-05-13 Thread Nathan Sidwell
On 5/13/20 2:44 AM, Christophe Lyon wrote: On Wed, 13 May 2020 at 02:24, H.J. Lu via Gcc-patches [PR 95013] Fix gcc.dg/unclosed-init.c 2020-05-13 Christophe Lyon PR preprocessor/95013 * gcc.dg/unclosed-init.c: Add missing comment in dg-error. Thanks for

Re: [PR 95013] EOF location is at end of file

2020-05-13 Thread Christophe Lyon via Gcc-patches
On Wed, 13 May 2020 at 02:24, H.J. Lu via Gcc-patches wrote: > > On Tue, May 12, 2020 at 2:24 PM Nathan Sidwell wrote: > > > > My recent C++ parser change to pay attention to EOF location uncovered a > > separate bug. The preprocesor's EOF logic would set the EOF location to > > be the

Re: [PR 95013] EOF location is at end of file

2020-05-12 Thread H.J. Lu via Gcc-patches
On Tue, May 12, 2020 at 2:24 PM Nathan Sidwell wrote: > > My recent C++ parser change to pay attention to EOF location uncovered a > separate bug. The preprocesor's EOF logic would set the EOF location to > be the beginning of the last line of text in the file -- not the 'line' > after that,

[PR 95013] EOF location is at end of file

2020-05-12 Thread Nathan Sidwell
My recent C++ parser change to pay attention to EOF location uncovered a separate bug. The preprocesor's EOF logic would set the EOF location to be the beginning of the last line of text in the file -- not the 'line' after that, which contains no characters. Mostly. This fixes things so