https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86907
Thomas Koenig changed:
What|Removed |Added
Status|WAITING |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86907
--- Comment #10 from Jürgen Reuter ---
(In reply to Thomas Koenig from comment #9)
> This makes the error message a litte bit clearer, to make sure
> it is understood that this is the compiler's fault, not the user's.
>
> However, I cannot repro
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86907
Thomas Koenig changed:
What|Removed |Added
Status|NEW |WAITING
--- Comment #9 from Thomas Koeni
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86907
--- Comment #8 from Thomas Koenig ---
Author: tkoenig
Date: Sat Oct 27 10:26:23 2018
New Revision: 265559
URL: https://gcc.gnu.org/viewcvs?rev=265559&root=gcc&view=rev
Log:
2018-10-27 Thomas Koenig
PR fortran/86907
* frontend
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86907
Thomas Koenig changed:
What|Removed |Added
Status|WAITING |NEW
CC|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86907
--- Comment #6 from Jürgen Reuter ---
Indeed, with --enable-checking=release on MACOSX and default option (which is
--enable-checking=yes) if I understand it correctly, the warning seems not to
be present. I didn't test --enable-checking=yes on M
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86907
Dominique d'Humieres changed:
What|Removed |Added
Status|UNCONFIRMED |WAITING
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86907
--- Comment #4 from janus at gcc dot gnu.org ---
(In reply to Jürgen Reuter from comment #3)
> Janus, this is actually incredibly valuable information. Yes, I was always
> since ages building gcc/gfortran/g++ from the svn, and at some point
> comp
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86907
--- Comment #3 from Jürgen Reuter ---
(In reply to janus from comment #2)
> I cannot reproduce this at r263854.
>
> I think the error you report requires GCC to be configured with
> --enable-checking (this is on by default for non-release builds
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86907
--- Comment #2 from janus at gcc dot gnu.org ---
I cannot reproduce this at r263854.
I think the error you report requires GCC to be configured with
--enable-checking (this is on by default for non-release builds, but off for
releases).
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86907
Richard Biener changed:
What|Removed |Added
Priority|P3 |P4
Target Milestone|---
11 matches
Mail list logo