public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "kargl at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/96013] ICE in write_symbol, at fortran/module.c:5747
Date: Fri, 26 Mar 2021 17:12:33 +0000	[thread overview]
Message-ID: <bug-96013-4-eXxYJoG2X1@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-96013-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #10 from kargl at gcc dot gnu.org ---
(In reply to Dominique d'Humieres from comment #9)
> > > Sometime the test ICE with
> > > 
> > > f951: internal compiler error: gfc_code2string(): Bad code
> > > 
> > > which cannot be fixed by the patch in comment 6.
> > > 
> >
> > Don't know anything about libsantize.  
> 
> The error has nothing to do with libsanitize.

So, then why are you posting incomprehensible garbage
from libsanitize, which may have absolutely nothing to
do with this patch.  The patch in comment #6 prevents
the segfault; thereby allowing f951 to continue with
the processing of the source code.

> It is generated by gfc_code2string in gcc/fortran/misc.c
> in a random manner.

I cannot reproduce your results. Without a method to
reproduce the issue and/or a complete backtrace with 
line numbers, I standby my assertion that the patch
in comment #6 fixes the segfault reported by Gerhard.
More importantly, it does not matter if the patch
fixes the segfault, because no one is going to commit
it anyway.

  parent reply	other threads:[~2021-03-26 17:12 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-30 20:12 [Bug fortran/96013] New: " gscfq@t-online.de
2020-06-30 20:12 ` [Bug fortran/96013] " gscfq@t-online.de
2020-06-30 20:47 ` kargl at gcc dot gnu.org
2020-06-30 21:00 ` kargl at gcc dot gnu.org
2020-06-30 21:22 ` kargl at gcc dot gnu.org
2020-06-30 21:38 ` kargl at gcc dot gnu.org
2020-06-30 21:41 ` kargl at gcc dot gnu.org
2021-03-26 12:08 ` dominiq at lps dot ens.fr
2021-03-26 16:04 ` kargl at gcc dot gnu.org
2021-03-26 16:30 ` dominiq at lps dot ens.fr
2021-03-26 17:12 ` kargl at gcc dot gnu.org [this message]
2021-03-27 13:56 ` dominiq at lps dot ens.fr
2021-03-27 13:59 ` dominiq at lps dot ens.fr
2021-04-18 11:27 ` dominiq at lps dot ens.fr
2021-04-18 17:34 ` kargl at gcc dot gnu.org

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-96013-4-eXxYJoG2X1@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).