[Bug fortran/93253] Regression on non-standard hex constant syntax

2020-01-16 Thread burnus at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93253 Tobias Burnus changed: What|Removed |Added CC||burnus at gcc dot gnu.org --- Comment

[Bug fortran/93253] Regression on non-standard hex constant syntax

2020-01-15 Thread cvs-commit at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93253 --- Comment #8 from CVS Commits --- The master branch has been updated by Tobias Burnus : https://gcc.gnu.org/g:c35a3046247c495509610b50c7a85683d540811a commit r10-5994-gc35a3046247c495509610b50c7a85683d540811a Author: Tobias Burnus Date:

[Bug fortran/93253] Regression on non-standard hex constant syntax

2020-01-14 Thread sgk at troutmask dot apl.washington.edu
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93253 --- Comment #7 from Steve Kargl --- On Tue, Jan 14, 2020 at 10:48:30AM +, fx at gnu dot org wrote: > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93253 > > --- Comment #4 from Dave Love --- > Apologies, I was misled by something else; that

[Bug fortran/93253] Regression on non-standard hex constant syntax

2020-01-14 Thread sgk at troutmask dot apl.washington.edu
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93253 --- Comment #6 from Steve Kargl --- On Tue, Jan 14, 2020 at 11:18:45AM +, pinskia at gcc dot gnu.org wrote: > CUT > So using an undocumented extension The 'X' extension was documented, but I doubt anyone reads documentation.

[Bug fortran/93253] Regression on non-standard hex constant syntax

2020-01-14 Thread pinskia at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93253 --- Comment #5 from Andrew Pinski --- By the way this is from the email thread that added that option (https://gcc.gnu.org/ml/fortran/2019-07/msg00054.html): The code for deprecated items is still present and can sometimes be used via the

[Bug fortran/93253] Regression on non-standard hex constant syntax

2020-01-14 Thread fx at gnu dot org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93253 --- Comment #4 from Dave Love --- Apologies, I was misled by something else; that option does affect the result. However, this change in behaviour isn't mentioned in release notes, the error message doesn't point to that option, and

[Bug fortran/93253] Regression on non-standard hex constant syntax

2020-01-14 Thread fx at gnu dot org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93253 --- Comment #3 from Dave Love --- You wrote: > Do you read the document that comes with your compiler? Do you appreciate how that sort of response sounds is likely to drive people off (not for the first time)? I read two sets of release

[Bug fortran/93253] Regression on non-standard hex constant syntax

2020-01-14 Thread markeggleston at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93253 markeggleston at gcc dot gnu.org changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED

[Bug fortran/93253] Regression on non-standard hex constant syntax

2020-01-13 Thread kargl at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93253 kargl at gcc dot gnu.org changed: What|Removed |Added CC||kargl at gcc dot gnu.org ---