public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dje at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/25252] ICE on invalid code
Date: Tue, 03 Jan 2006 16:25:00 -0000 [thread overview]
Message-ID: <20060103162536.23979.qmail@sourceware.org> (raw)
In-Reply-To: <bug-25252-8649@http.gcc.gnu.org/bugzilla/>
------- Comment #2 from dje at gcc dot gnu dot org 2006-01-03 16:25 -------
Not powerpc-specific.
--
dje at gcc dot gnu dot org changed:
What |Removed |Added
----------------------------------------------------------------------------
GCC build triplet|powerpc64-linux |
GCC host triplet|powerpc64-linux |
GCC target triplet|powerpc64-linux |
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=25252
next prev parent reply other threads:[~2006-01-03 16:25 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-04 19:25 [Bug regression/25252] New: " uttamp at us dot ibm dot com
2005-12-10 20:30 ` [Bug fortran/25252] " eedelman at gcc dot gnu dot org
2006-01-03 16:25 ` dje at gcc dot gnu dot org [this message]
2006-08-29 21:39 ` kargl at gcc dot gnu dot org
2006-09-16 20:06 ` pault at gcc dot gnu dot org
2007-02-15 20:51 ` kargl at gcc dot gnu dot org
2007-02-15 21:43 ` dominiq at lps dot ens dot fr
2007-03-10 22:15 ` reichelt at gcc dot gnu dot org
2007-05-13 22:36 ` jvdelisle at gcc dot gnu dot org
2007-05-18 20:27 ` reichelt at gcc dot gnu dot org
2007-05-21 19:16 ` dfranke at gcc dot gnu dot org
2007-06-02 8:30 ` jvdelisle at gcc dot gnu dot org
2007-06-07 22:56 ` reichelt at gcc dot gnu dot org
2007-06-08 0:46 ` jvdelisle at gcc dot gnu dot org
2007-11-02 9:55 ` reichelt at gcc dot gnu dot org
2007-11-02 13:18 ` jvdelisle at gcc dot gnu dot org
2007-11-10 0:53 ` fxcoudert at gcc dot gnu dot org
2007-11-17 16:55 ` fxcoudert at gcc dot gnu dot org
2007-11-17 17:50 ` fxcoudert at gcc dot gnu dot org
2007-11-17 17:54 ` fxcoudert at gcc dot gnu dot org
2007-11-20 5:03 ` patchapp at dberlin 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=20060103162536.23979.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).