public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dave at hiauly1 dot hia dot nrc dot ca" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/28176] FAIL: gfortran.dg/actual_array_constructor_1.f90 -O0 (ICE)
Date: Wed, 18 Oct 2006 18:51:00 -0000 [thread overview]
Message-ID: <20061018185118.13781.qmail@sourceware.org> (raw)
In-Reply-To: <bug-28176-276@http.gcc.gnu.org/bugzilla/>
------- Comment #5 from dave at hiauly1 dot hia dot nrc dot ca 2006-10-18 18:51 -------
Subject: Re: FAIL: gfortran.dg/actual_array_constructor_1.f90 -O0 (ICE)
> Looking at my old logs it looks like gfortran.dg/actual_array_constructor_1.f90
> has been failing on hppa64 since it first went in on April 21, 2006. Someone
> is creating a TImode variable even though hppa64 doesn't support them. I
> haven't been able to figure out who though.
Right. I think figuring out who is creating the variable will
help to understand and fix the bug.
Dave
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=28176
next prev parent reply other threads:[~2006-10-18 18:51 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-27 1:47 [Bug fortran/28176] New: " danglin at gcc dot gnu dot org
2006-06-27 2:44 ` [Bug fortran/28176] " danglin at gcc dot gnu dot org
2006-06-28 14:32 ` pault at gcc dot gnu dot org
2006-07-06 16:49 ` danglin at gcc dot gnu dot org
2006-10-18 18:16 ` sje at cup dot hp dot com
2006-10-18 18:51 ` dave at hiauly1 dot hia dot nrc dot ca [this message]
2006-10-18 20:49 ` sje at cup dot hp dot com
2006-10-19 1:56 ` dave at hiauly1 dot hia dot nrc dot ca
2006-10-19 18:09 ` sje at cup dot hp dot com
2006-10-22 16:18 ` [Bug middle-end/28176] " dave at hiauly1 dot hia dot nrc dot ca
2006-11-18 23:17 ` danglin at gcc dot gnu dot org
2006-11-19 0:44 ` danglin at gcc dot gnu dot org
2006-11-19 0:50 ` danglin at gcc dot gnu dot org
2006-12-01 2:06 ` chaoyingfu 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=20061018185118.13781.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).