[Bug fortran/86907] [9 Regression] bogus warning "No location in expression near"
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86907 Thomas Koenig changed: What|Removed |Added Status|WAITING |RESOLVED Resolution|--- |WORKSFORME --- Comment #11 from Thomas Koenig --- OK, sowe can close this.
[Bug fortran/86907] [9 Regression] bogus warning "No location in expression near"
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 reproduce the original problem. Dear Thomas, I didn't check your changes (but they only modify the warning message as far as I understand). I already confirmed to Dominique that for the code I submitted (and also our full code) the warning does not appear any more.
[Bug fortran/86907] [9 Regression] bogus warning "No location in expression near"
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86907 Thomas Koenig changed: What|Removed |Added Status|NEW |WAITING --- Comment #9 from Thomas Koenig --- 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 reproduce the original problem.
[Bug fortran/86907] [9 Regression] bogus warning "No location in expression near"
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=gcc=rev Log: 2018-10-27 Thomas Koenig PR fortran/86907 * frontend-passes.c (check_locus_code): Add information that warning about missing location information points to an inconsisten internal state. (check_locus_expr): Likewise. Modified: trunk/gcc/fortran/ChangeLog trunk/gcc/fortran/frontend-passes.c
[Bug fortran/86907] [9 Regression] bogus warning "No location in expression near"
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86907 Thomas Koenig changed: What|Removed |Added Status|WAITING |NEW CC||tkoenig at gcc dot gnu.org --- Comment #7 from Thomas Koenig --- The idea is to find pieces of code which (gfortran internally) do not have information about where they are. If an error occurs which involves such a piece of code, an ICE would occur. This is mostly done to catch cases when a patch forgets to add this info - it shiws uo on regression testing right away. This is also why this is disabled with checking=release. Maybe we should do something about the warning to make it clearer that this is internal - suggestions welcome. We should also find out where copying localization does not happen.
[Bug fortran/86907] [9 Regression] bogus warning "No location in expression near"
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 MACOSX but I believe this could be closed as WORKSFORME.
[Bug fortran/86907] [9 Regression] bogus warning "No location in expression near"
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86907 Dominique d'Humieres changed: What|Removed |Added Status|UNCONFIRMED |WAITING Last reconfirmed||2018-10-25 Ever confirmed|0 |1 --- Comment #5 from Dominique d'Humieres --- I cannot reproduce it on x86_64-apple-darwin17 with various revisions configured with --enable-checking=release or --enable-checking=yes.
[Bug fortran/86907] [9 Regression] bogus warning "No location in expression near"
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
> compilation became significantly ("macroscopically") slower, probably from
> version 7.0.0 on. Could this be when enable-checking was introduced.
I'm pretty sure --enable-checking exists much longer than that, but maybe the
default has changed at some point?
> Can I just compile the svn version with --enable-checking=release?
Sure!
[Bug fortran/86907] [9 Regression] bogus warning "No location in expression near"
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, but off for
> releases).
Janus, this is actually incredibly valuable information. Yes, I was always
since ages building gcc/gfortran/g++ from the svn, and at some point
compilation became significantly ("macroscopically") slower, probably from
version 7.0.0 on. Could this be when enable-checking was introduced. Can I just
compile the svn version with --enable-checking=release?
[Bug fortran/86907] [9 Regression] bogus warning "No location in expression near"
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).
[Bug fortran/86907] [9 Regression] bogus warning "No location in expression near"
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86907 Richard Biener changed: What|Removed |Added Priority|P3 |P4 Target Milestone|--- |9.0 Summary|[9.0 regression] bogus |[9 Regression] bogus |warning "No location in |warning "No location in |expression near"|expression near"
