[Bug fortran/68040] [5/6 Regression] Internal compiler error: Error reporting routines re-entered.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68040 Richard Biener changed: What|Removed |Added Target Milestone|5.3 |5.4 --- Comment #4 from Richard Biener --- GCC 5.3 is being released, adjusting target milestone.
[Bug fortran/68040] [5/6 Regression] Internal compiler error: Error reporting routines re-entered.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68040 --- Comment #3 from Manuel López-Ibáñez --- (In reply to Dominique d'Humieres from comment #2) > > However, I would argue that this precise warning does not need to use > > %E and it could simply use %s, which will make it less dependent on trees > > and fix this bug without further changes in Fortran. > > Where should I do the change? #13 0x000100ca61f1 in decl_attributes (node=, attributes=, flags=) at ../../_clean/gcc/attribs.c:446 But you need to figure out how to get the const char* pointing to the attribute name from the tree passed to %E.
[Bug fortran/68040] [5/6 Regression] Internal compiler error: Error reporting routines re-entered.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68040 --- Comment #2 from Dominique d'Humieres --- > Is this configured with --enable-checking=release ? This is probably an ICE > that occurs earlier than reported with --enabled-checking=release. > Configure with --enable-checking=yes. I get the same ICE with trunk configured with ../work/configure --prefix=/opt/gcc/gcc6w --enable-languages=c,c++,fortran,objc,obj-c++,ada,java,lto --with-gmp=/opt/mp-new --with-system-zlib --with-isl=/opt/mp-new --enable-lto --enable-plugin --with-arch=corei7 --with-cpu=corei7 or configured with ../p_work/configure --prefix=/opt/gcc/gcc6p-229482 --enable-languages=c,c++,lto,fortran,ada,objc,obj-c++ --with-gmp=/opt/mp-new --with-system-zlib --enable-checking=release --with-isl=/opt/mp-new --enable-lto --enable-plugin --with-arch=core2 --with-cpu=core2 > It should be possible to get a more precise revision. Those two do not look > like the cause of the problem. I see the ICE with r217500, but I don't have any revision between r217100 and r217500. Note that I don't say the problem is caused by one of these revisions, they are the revision numbers given by SVN for which I see the different behaviors (Warning vs. ICE). > However, I would argue that this precise warning does not need to use > %E and it could simply use %s, which will make it less dependent on trees > and fix this bug without further changes in Fortran. Where should I do the change?
[Bug fortran/68040] [5/6 Regression] Internal compiler error: Error reporting routines re-entered.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68040 Dominique d'Humieres changed: What|Removed |Added Status|UNCONFIRMED |NEW Last reconfirmed||2015-10-28 Ever confirmed|0 |1
[Bug fortran/68040] [5/6 Regression] Internal compiler error: Error reporting routines re-entered.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68040 Manuel López-Ibáñez changed: What|Removed |Added CC||manu at gcc dot gnu.org --- Comment #1 from Manuel López-Ibáñez --- Is this configured with --enable-checking=release ? This is probably an ICE that occurs earlier than reported with --enabled-checking=release. Configure with --enable-checking=yes. It should be possible to get a more precise revision. Those two do not look like the cause of the problem. My guess is that Fortran is calling into the middle-end without calling gfc_diagnostics_finish(). The format decoder gfc_format_decoder does not support %E, thus either Fortran adds support for %E or it calls gfc_diagnostic_finish before reaching this point. However, I would argue that this precise warning does not need to use %E and it could simply use %s, which will make it less dependent on trees and fix this bug without further changes in Fortran.
[Bug fortran/68040] [5/6 Regression] Internal compiler error: Error reporting routines re-entered.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68040 Richard Biener changed: What|Removed |Added Priority|P3 |P4 Target Milestone|--- |5.3
