public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pault at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/37992] [4.4 Regression] ICE segfault for "character(len=len(x)) :: foo,x"
Date: Tue, 04 Nov 2008 08:00:00 -0000	[thread overview]
Message-ID: <20081104075915.14849.qmail@sourceware.org> (raw)
In-Reply-To: <bug-37992-13404@http.gcc.gnu.org/bugzilla/>



------- Comment #6 from pault at gcc dot gnu dot org  2008-11-04 07:59 -------
(In reply to comment #5)
> The patch in comment #4 generate a lot of bus errors in my tests. Looking at
> it, I think there is something missing: gfc_current_ns->old_cl_list is only set
> to NULL, it should likely be set to gfc_current_ns->cl_list somewhere.
> 
It should not be necessary to do anything to the cl_list.  As long as nothing
points to a member, it can do nothing and gets cleaned up at the end of
compilation. The reason for this is that any number, including zero, of
typespecs can point to it, so it is very risky to delete a cl_list member.

Paul

Paul


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=37992


  parent reply	other threads:[~2008-11-04  8:00 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-01 22:05 [Bug fortran/37992] New: " burnus at gcc dot gnu dot org
2008-11-01 22:39 ` [Bug fortran/37992] " burnus at gcc dot gnu dot org
2008-11-01 22:44 ` janus at gcc dot gnu dot org
2008-11-02 17:51 ` mikael dot morin at tele2 dot fr
2008-11-02 18:04 ` mikael dot morin at tele2 dot fr
2008-11-03 11:03 ` dominiq at lps dot ens dot fr
2008-11-04  8:00 ` pault at gcc dot gnu dot org [this message]
2008-11-05 14:03 ` mikael at gcc dot gnu dot org
2008-11-05 17:03 ` [Bug fortran/37992] ICE while resolving charlen for rejected statements mikael at gcc dot gnu dot org
2008-11-05 18:48 ` mikael at gcc dot gnu dot org
2008-11-05 22:30 ` dominiq at lps dot ens dot fr
2008-11-16 20:47 ` mikael at gcc dot gnu dot org
2008-11-16 21:06 ` mikael at gcc dot gnu dot 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=20081104075915.14849.qmail@sourceware.org \
    --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).