gfortran Error Parser (gfortran 5.x)

classic Classic list List threaded Threaded
5 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

gfortran Error Parser (gfortran 5.x)

Luke Robison
I am using PTP as downloaded from the stand-alone Eclipse Neon.2 PTP ('eclipse-parallel-neon-2-linux-gtk-x86_64').

I am using gfortran 5.1 and Make to compile (and this all works well), but I cannot get the "Photran Error Parser for GNU Fortran (gfortran)" to recognize my errors correctly.  This same issue seems to have been found by Holger previously on this mailing list but I could find no solution.

I believe Holger correctly outlines the problem: gfortran's line and character delimiter within the error message switched from "." to ":" somewhere between gfortran 4 and 5.  Not only does this fail to find the correct line, but it also seems to make the file search fail.  As a result, the errors are not clickable and do not show up in the editor.

Is there a way I can edit the parser to recognize this change?  I do not see an "edit" option like I do on other parsers.

I also did not find a bug related to this issue, although I did follow a recommendation to ensure that the gfortran parser is being used, NOT the gcc error parser.

Thanks,
Luke Robison


I'll copy Holger's email below (from 2015):

4.8:
$ gfortran -o delme delme.f90
delme.f90:4.2:

i = i + 1
1
Error: Named constant 'i' in variable definition context (assignment) at (1)

5.1:
$ gfortran -o delme delme.f90
delme.f90:4:2:

i = i + 1
1
Error: Named constant 'i' in variable definition context (assignment) at (1)

Notice the delimiter between the line number (4) and the position (2). It's a point in v4.8, and a colon in v5.1

How do I change the error parser to reflect this change? Thanks
Holger



_______________________________________________
ptp-dev mailing list
[hidden email]
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/ptp-dev

smime.p7s (7K) Download Attachment
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: gfortran Error Parser (gfortran 5.x)

Greg Watson-2
Hi Luke,

There is no easy way for a user to change this. I've opened bug #512600 on the issue (https://bugs.eclipse.org/bugs/show_bug.cgi?id=512600).

Regards,
Greg

On Feb 22, 2017, at 3:29 PM, Luke Robison <[hidden email]> wrote:

I am using PTP as downloaded from the stand-alone Eclipse Neon.2 PTP ('eclipse-parallel-neon-2-linux-gtk-x86_64').

I am using gfortran 5.1 and Make to compile (and this all works well), but I cannot get the "Photran Error Parser for GNU Fortran (gfortran)" to recognize my errors correctly.  This same issue seems to have been found by Holger previously on this mailing list but I could find no solution.

I believe Holger correctly outlines the problem: gfortran's line and character delimiter within the error message switched from "." to ":" somewhere between gfortran 4 and 5.  Not only does this fail to find the correct line, but it also seems to make the file search fail.  As a result, the errors are not clickable and do not show up in the editor.

Is there a way I can edit the parser to recognize this change?  I do not see an "edit" option like I do on other parsers.

I also did not find a bug related to this issue, although I did follow a recommendation to ensure that the gfortran parser is being used, NOT the gcc error parser.

Thanks,
Luke Robison


I'll copy Holger's email below (from 2015):

4.8:
$ gfortran -o delme delme.f90
delme.f90:4.2:

i = i + 1
1
Error: Named constant 'i' in variable definition context (assignment) at (1)

5.1:
$ gfortran -o delme delme.f90
delme.f90:4:2:

i = i + 1
1
Error: Named constant 'i' in variable definition context (assignment) at (1)

Notice the delimiter between the line number (4) and the position (2). It's a point in v4.8, and a colon in v5.1

How do I change the error parser to reflect this change? Thanks
Holger


_______________________________________________
ptp-dev mailing list
[hidden email]
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/ptp-dev


_______________________________________________
ptp-dev mailing list
[hidden email]
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/ptp-dev
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: gfortran Error Parser (gfortran 5.x)

Greg Watson-2
I've fixed this in the latest PTP milestone build [1]. If you would like to try it out, I'd appreciate the feedback. I only have gfortran 6.x installed, but I'm assuming it will work with 5.x as the errors seem the same. It would be good to also test it with 4.x to make sure I haven't introduced a regression. 

The fix will be available in Neon.3 when it is released.

Thanks,
Greg

[1] http://download.eclipse.org/tools/ptp/builds/neon/milestones/


On Feb 22, 2017, at 7:40 PM, Greg Watson <[hidden email]> wrote:

Hi Luke,

There is no easy way for a user to change this. I've opened bug #512600 on the issue (https://bugs.eclipse.org/bugs/show_bug.cgi?id=512600).

Regards,
Greg

On Feb 22, 2017, at 3:29 PM, Luke Robison <[hidden email]> wrote:

I am using PTP as downloaded from the stand-alone Eclipse Neon.2 PTP ('eclipse-parallel-neon-2-linux-gtk-x86_64').

I am using gfortran 5.1 and Make to compile (and this all works well), but I cannot get the "Photran Error Parser for GNU Fortran (gfortran)" to recognize my errors correctly.  This same issue seems to have been found by Holger previously on this mailing list but I could find no solution.

I believe Holger correctly outlines the problem: gfortran's line and character delimiter within the error message switched from "." to ":" somewhere between gfortran 4 and 5.  Not only does this fail to find the correct line, but it also seems to make the file search fail.  As a result, the errors are not clickable and do not show up in the editor.

Is there a way I can edit the parser to recognize this change?  I do not see an "edit" option like I do on other parsers.

I also did not find a bug related to this issue, although I did follow a recommendation to ensure that the gfortran parser is being used, NOT the gcc error parser.

Thanks,
Luke Robison


I'll copy Holger's email below (from 2015):

4.8:
$ gfortran -o delme delme.f90
delme.f90:4.2:

i = i + 1
1
Error: Named constant 'i' in variable definition context (assignment) at (1)

5.1:
$ gfortran -o delme delme.f90
delme.f90:4:2:

i = i + 1
1
Error: Named constant 'i' in variable definition context (assignment) at (1)

Notice the delimiter between the line number (4) and the position (2). It's a point in v4.8, and a colon in v5.1

How do I change the error parser to reflect this change? Thanks
Holger


_______________________________________________
ptp-dev mailing list
[hidden email]
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/ptp-dev

_______________________________________________
ptp-dev mailing list
[hidden email]
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/ptp-dev


_______________________________________________
ptp-dev mailing list
[hidden email]
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/ptp-dev
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: gfortran Error Parser (gfortran 5.x)

Luke Robison
In reply to this post by Luke Robison
Greg,

Thanks for the quick response.  I've verified the error parser for
Neon.3 RC2 works on both gfortran 5.3 and 4.8!  This is very helpful.

Luke

> Date: Wed, 22 Feb 2017 20:32:33 -0500
> From: Greg Watson<[hidden email]>
>
>
> I've fixed this in the latest PTP milestone build [1]. If you would like to try it out, I'd appreciate the feedback. I only have gfortran 6.x installed, but I'm assuming it will work with 5.x as the errors seem the same. It would be good to also test it with 4.x to make sure I haven't introduced a regression.
>
> The fix will be available in Neon.3 when it is released.
>
> Thanks,
> Greg
>
> [1]http://download.eclipse.org/tools/ptp/builds/neon/milestones/
>
>
>> On Feb 22, 2017, at 7:40 PM, Greg Watson<[hidden email]>  wrote:
>>
>> Hi Luke,
>>
>> There is no easy way for a user to change this. I've opened bug #512600 on the issue (https://bugs.eclipse.org/bugs/show_bug.cgi?id=512600  <https://bugs.eclipse.org/bugs/show_bug.cgi?id=512600>).
>>
>> Regards,
>> Greg
>>
>>> On Feb 22, 2017, at 3:29 PM, Luke Robison <[hidden email]  <mailto:[hidden email]>> wrote:
>>>
>>> I am using PTP as downloaded from the stand-alone Eclipse Neon.2 PTP ('eclipse-parallel-neon-2-linux-gtk-x86_64').
>>>
>>> I am using gfortran 5.1 and Make to compile (and this all works well), but I cannot get the "Photran Error Parser for GNU Fortran (gfortran)" to recognize my errors correctly.  This same issue seems to have been found by Holger previously on this mailing list but I could find no solution.
>>>
>>> I believe Holger correctly outlines the problem: gfortran's line and character delimiter within the error message switched from "." to ":" somewhere between gfortran 4 and 5.  Not only does this fail to find the correct line, but it also seems to make the file search fail.  As a result, the errors are not clickable and do not show up in the editor.
>>>
>>> Is there a way I can edit the parser to recognize this change?  I do not see an "edit" option like I do on other parsers.
>>>
>>> I also did not find a bug related to this issue, although I did follow a recommendation to ensure that the gfortran parser is being used, NOT the gcc error parser.
>>>
>>> Thanks,
>>> Luke Robison
>>>
>>>
>>> I'll copy Holger's email below (from 2015):
>>>
>>>   4.8:
>>> $ gfortran -o delme delme.f90
>>> delme.f90:4.2:
>>>
>>> i = i + 1
>>> 1
>>> Error: Named constant 'i' in variable definition context (assignment) at (1)
>>>
>>>   5.1:
>>> $ gfortran -o delme delme.f90
>>> delme.f90:4:2:
>>>
>>> i = i + 1
>>> 1
>>> Error: Named constant 'i' in variable definition context (assignment) at (1)
>>>
>>> Notice the delimiter between the line number (4) and the position (2). It's a point in v4.8, and a colon in v5.1
>>>
>>>   How do I change the error parser to reflect this change? Thanks
>>> Holger
>>>
>>>
>>> _______________________________________________
>>> ptp-dev mailing list
>>> [hidden email]  <mailto:[hidden email]>
>>> To change your delivery options, retrieve your password, or unsubscribe from this list, visit
>>> https://dev.eclipse.org/mailman/listinfo/ptp-dev
>> _______________________________________________
>> ptp-dev mailing list
>> [hidden email]
>> To change your delivery options, retrieve your password, or unsubscribe from this list, visit
>> https://dev.eclipse.org/mailman/listinfo/ptp-dev

_______________________________________________
ptp-dev mailing list
[hidden email]
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/ptp-dev

smime.p7s (7K) Download Attachment
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: gfortran Error Parser (gfortran 5.x)

Greg Watson-2
Great, thanks for testing it.

Regards,
Greg

> On Feb 28, 2017, at 5:43 PM, Luke Robison <[hidden email]> wrote:
>
> Greg,
>
> Thanks for the quick response.  I've verified the error parser for Neon.3 RC2 works on both gfortran 5.3 and 4.8!  This is very helpful.
>
> Luke
>
>> Date: Wed, 22 Feb 2017 20:32:33 -0500
>> From: Greg Watson<[hidden email]>
>>
>>
>> I've fixed this in the latest PTP milestone build [1]. If you would like to try it out, I'd appreciate the feedback. I only have gfortran 6.x installed, but I'm assuming it will work with 5.x as the errors seem the same. It would be good to also test it with 4.x to make sure I haven't introduced a regression.
>>
>> The fix will be available in Neon.3 when it is released.
>>
>> Thanks,
>> Greg
>>
>> [1]http://download.eclipse.org/tools/ptp/builds/neon/milestones/
>>
>>
>>> On Feb 22, 2017, at 7:40 PM, Greg Watson<[hidden email]>  wrote:
>>>
>>> Hi Luke,
>>>
>>> There is no easy way for a user to change this. I've opened bug #512600 on the issue (https://bugs.eclipse.org/bugs/show_bug.cgi?id=512600  <https://bugs.eclipse.org/bugs/show_bug.cgi?id=512600>).
>>>
>>> Regards,
>>> Greg
>>>
>>>> On Feb 22, 2017, at 3:29 PM, Luke Robison <[hidden email]  <mailto:[hidden email]>> wrote:
>>>>
>>>> I am using PTP as downloaded from the stand-alone Eclipse Neon.2 PTP ('eclipse-parallel-neon-2-linux-gtk-x86_64').
>>>>
>>>> I am using gfortran 5.1 and Make to compile (and this all works well), but I cannot get the "Photran Error Parser for GNU Fortran (gfortran)" to recognize my errors correctly.  This same issue seems to have been found by Holger previously on this mailing list but I could find no solution.
>>>>
>>>> I believe Holger correctly outlines the problem: gfortran's line and character delimiter within the error message switched from "." to ":" somewhere between gfortran 4 and 5.  Not only does this fail to find the correct line, but it also seems to make the file search fail.  As a result, the errors are not clickable and do not show up in the editor.
>>>>
>>>> Is there a way I can edit the parser to recognize this change?  I do not see an "edit" option like I do on other parsers.
>>>>
>>>> I also did not find a bug related to this issue, although I did follow a recommendation to ensure that the gfortran parser is being used, NOT the gcc error parser.
>>>>
>>>> Thanks,
>>>> Luke Robison
>>>>
>>>>
>>>> I'll copy Holger's email below (from 2015):
>>>>
>>>>  4.8:
>>>> $ gfortran -o delme delme.f90
>>>> delme.f90:4.2:
>>>>
>>>> i = i + 1
>>>> 1
>>>> Error: Named constant 'i' in variable definition context (assignment) at (1)
>>>>
>>>>  5.1:
>>>> $ gfortran -o delme delme.f90
>>>> delme.f90:4:2:
>>>>
>>>> i = i + 1
>>>> 1
>>>> Error: Named constant 'i' in variable definition context (assignment) at (1)
>>>>
>>>> Notice the delimiter between the line number (4) and the position (2). It's a point in v4.8, and a colon in v5.1
>>>>
>>>>  How do I change the error parser to reflect this change? Thanks
>>>> Holger
>>>>
>>>>
>>>> _______________________________________________
>>>> ptp-dev mailing list
>>>> [hidden email]  <mailto:[hidden email]>
>>>> To change your delivery options, retrieve your password, or unsubscribe from this list, visit
>>>> https://dev.eclipse.org/mailman/listinfo/ptp-dev
>>> _______________________________________________
>>> ptp-dev mailing list
>>> [hidden email]
>>> To change your delivery options, retrieve your password, or unsubscribe from this list, visit
>>> https://dev.eclipse.org/mailman/listinfo/ptp-dev
>
> _______________________________________________
> ptp-dev mailing list
> [hidden email]
> To change your delivery options, retrieve your password, or unsubscribe from this list, visit
> https://dev.eclipse.org/mailman/listinfo/ptp-dev

_______________________________________________
ptp-dev mailing list
[hidden email]
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/ptp-dev
Loading...