This is the mail archive of the gcc-bugs@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Bug fortran/67429] [5/6 Regression] Missing part of error messages.


https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67429

--- Comment #11 from Dominique d'Humieres <dominiq at lps dot ens.fr> ---
(In reply to Manuel LÃpez-IbÃÃez  from comment #10)

> > Error: Expecting END BLOCK statement at (1)
> > (null):0: confused by earlier errors, bailing out
>
>
> Even if *I* cannot reproduce this, such an error should be easy to debug:
> Just put a break in diagnostic_report_diagnostic on the line that gives
> this message and go up to find out what triggered this code to run.
> My guess is that you are somehow triggering an ICE while reporting an ICE.
> It would be interesting to understand where that strange location comes
> from (I guess it is UNKNOWN_LOCATION?). And also to harden that code to not
> try to print a null s.file pointer!

Sorry for the confusion I sometime get this kind of error instead of the usual
ICE when using compilers configured with '--enable-checking=release'.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]