public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "c dot lemmen at fz-juelich dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/16382] ice-on [in?]valid code REG_DEAD
Date: Tue, 31 Aug 2004 07:46:00 -0000 [thread overview]
Message-ID: <20040831074623.3043.qmail@sourceware.org> (raw)
In-Reply-To: <20040706104357.16382.c.lemmen@fz-juelich.de>
------- Additional Comments From c dot lemmen at fz-juelich dot de 2004-08-31 07:46 -------
Yep, trying again... and getting further but not quite there yet! At least I'm
not running int 12840 related stuff any more. However, this one is now
blocked by PR 17244 and another unreported bug. Which I'm not reporting since I
don't know whether the code's correct but all other compilers do compile while
gfortran only says:
internal compiler error: Segmentation fault
I tried to isolate the segfault to make a proper PR but I wasn't able to track
down the error, will try later (2 weeks from now...)
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=16382
next prev parent reply other threads:[~2004-08-31 7:46 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-06 10:44 [Bug fortran/16382] New: " c dot lemmen at fz-juelich dot de
2004-07-06 15:39 ` [Bug fortran/16382] " pinskia at gcc dot gnu dot org
2004-07-12 13:12 ` c dot lemmen at fz-juelich dot de
2004-07-12 14:46 ` pinskia at gcc dot gnu dot org
2004-07-13 7:15 ` c dot lemmen at fz-juelich dot de
2004-07-15 20:00 ` tobi at gcc dot gnu dot org
2004-07-16 9:56 ` c dot lemmen at fz-juelich dot de
2004-07-19 9:27 ` c dot lemmen at fz-juelich dot de
2004-08-31 5:58 ` pinskia at gcc dot gnu dot org
2004-08-31 7:46 ` c dot lemmen at fz-juelich dot de [this message]
2004-08-31 16:57 ` tobi at gcc dot gnu dot org
2004-09-01 7:40 ` c dot lemmen at fz-juelich dot de
2004-09-16 9:31 ` c dot lemmen at fz-juelich dot de
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=20040831074623.3043.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).