public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "amodra at bigpond dot net dot au" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/26459] [4.1/4.2 Regression] gcc fails to build on powerpc e500-double targets
Date: Sat, 25 Mar 2006 02:59:00 -0000	[thread overview]
Message-ID: <20060325025946.9617.qmail@sourceware.org> (raw)
In-Reply-To: <bug-26459-12262@http.gcc.gnu.org/bugzilla/>



-- 

amodra at bigpond dot net dot au changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         AssignedTo|unassigned at gcc dot gnu   |amodra at bigpond dot net
                   |dot org                     |dot au
             Status|NEW                         |ASSIGNED
   Last reconfirmed|2006-02-24 18:42:12         |2006-03-25 02:59:46
               date|                            |


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


  parent reply	other threads:[~2006-03-25  2:59 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-24 18:42 [Bug c/26459] New: gcc-4.1.0 RC2 fails to build on certain PowerPC targets edmar at freescale dot com
2006-02-24 18:43 ` [Bug target/26459] [4.1/4.2 Regression] gcc-4.1.0 RC2 fails to build on powerpc e500-double targets pinskia at gcc dot gnu dot org
2006-02-24 18:45 ` [Bug target/26459] [4.1/4.2 Regression] gcc " pinskia at gcc dot gnu dot org
2006-02-24 18:54 ` edmar at freescale dot com
2006-02-24 19:10 ` mmitchel at gcc dot gnu dot org
2006-02-24 19:13 ` edmar at freescale dot com
2006-02-24 19:29 ` mark at codesourcery dot com
2006-02-24 20:48 ` edmar at freescale dot com
2006-02-24 21:14 ` mark at codesourcery dot com
2006-02-24 21:17 ` edmar at freescale dot com
2006-02-24 22:03 ` mmitchel at gcc dot gnu dot org
2006-02-27 21:42 ` steven at gcc dot gnu dot org
2006-02-27 22:42 ` steven at gcc dot gnu dot org
2006-02-27 22:43 ` steven at gcc dot gnu dot org
2006-02-27 22:53 ` steven at gcc dot gnu dot org
2006-02-28 20:35 ` mmitchel at gcc dot gnu dot org
2006-03-24 14:23 ` amodra at bigpond dot net dot au
2006-03-25  2:59 ` amodra at bigpond dot net dot au [this message]
2006-03-25  3:01 ` amodra at bigpond dot net dot au
2006-03-26 22:48 ` amodra at gcc dot gnu dot org
2006-03-26 22:49 ` amodra at gcc dot gnu dot org
2006-03-27  1:41 ` amodra at bigpond dot net dot au
2006-03-27  4:36 ` patchapp at dberlin dot org
2006-03-31  1:25 ` amodra at gcc dot gnu dot org
2006-03-31  1:27 ` amodra at gcc dot gnu dot org
2006-03-31  1:54 ` amodra at bigpond dot net dot au
2006-04-10 15:42 ` edmar at freescale dot com
2006-04-11  0:33 ` amodra at gcc dot gnu dot org
2006-04-11  0:36 ` amodra at gcc dot gnu dot org
2006-04-11  0:37 ` amodra at bigpond dot net dot au
2006-04-12 15:36 ` edmar at freescale dot com
2006-04-13  5:10 ` amodra at gcc dot gnu dot org
2006-04-13  5:46 ` amodra at gcc dot gnu dot org
2006-04-16 18:39 ` mmitchel at gcc dot gnu dot org
2006-04-17  0:09 ` amodra at bigpond dot net dot au
2006-04-17 15:22 ` edmar at freescale dot com
2006-04-17 15:37 ` mark at codesourcery dot com
2006-04-17 15:44 ` edmar at freescale dot com

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=20060325025946.9617.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).