On Fri, May 04, 2018 at 02:05:11PM -0600, Jeff Law wrote:
> On 05/04/2018 01:55 PM, Steve Kargl wrote:
> > On Fri, May 04, 2018 at 01:32:00PM -0600, Jeff Law wrote:
> >>
> >> The Fortran front end has its own code to parse #
> >> directives. We've run into a case where it does not function corre
On 05/04/2018 01:55 PM, Steve Kargl wrote:
> On Fri, May 04, 2018 at 01:32:00PM -0600, Jeff Law wrote:
>>
>> The Fortran front end has its own code to parse #
>> directives. We've run into a case where it does not function correctly.
>> In particular when the directive changes the current file,
On Fri, May 04, 2018 at 01:32:00PM -0600, Jeff Law wrote:
>
> The Fortran front end has its own code to parse #
> directives. We've run into a case where it does not function correctly.
> In particular when the directive changes the current file, subsequent
> diagnostics still refer to the ori
The Fortran front end has its own code to parse #
directives. We've run into a case where it does not function correctly.
In particular when the directive changes the current file, subsequent
diagnostics still refer to the original filename.
Concretely take this code and compile it with -Wall
