From: kenner@vlsi1.ultra.nyu.edu (Richard Kenner)
To: graham.stott@btinternet.com
Cc: fortran@gcc.gnu.org, gcc@gcc.gnu.org,
tobias.schlueter@physik.uni-muenchen.de
Subject: Re: Your patch causes regression in the Fortran frontend
Date: Thu, 23 Sep 2004 18:12:00 -0000 [thread overview]
Message-ID: <10409231551.AA21442@vlsi1.ultra.nyu.edu> (raw)
Could this be related to the problem Kenner found yesterday with
inlining and shared INTEGER_CST nodes being incorrectly modified
during inlining?
Seems very highly unlikely to me since the problem I ran into should
only affect types that have variable bounds and I don't think Fortran
does that. Also, that ICE is very specific.
In any event, I'm about to check in the fix for the problem I found,
so you'll know for sure then.
next reply other threads:[~2004-09-23 15:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-23 18:12 Richard Kenner [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-09-21 18:22 Tobias Schlüter
2004-09-23 16:31 ` Tobias Schlüter
2004-09-23 16:49 ` Graham Stott
2004-09-23 23:55 ` Richard Henderson
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=10409231551.AA21442@vlsi1.ultra.nyu.edu \
--to=kenner@vlsi1.ultra.nyu.edu \
--cc=fortran@gcc.gnu.org \
--cc=gcc@gcc.gnu.org \
--cc=graham.stott@btinternet.com \
--cc=tobias.schlueter@physik.uni-muenchen.de \
/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).