public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug optimization/14053] second stage build errors (--with-cpu=601)
Date: Fri, 20 Feb 2004 21:51:00 -0000 [thread overview]
Message-ID: <20040220215113.3399.qmail@sources.redhat.com> (raw)
In-Reply-To: <20040206230200.14053.stefaan.simoens@tiscali.be>
------- Additional Comments From pinskia at gcc dot gnu dot org 2004-02-20 21:51 -------
The real issue here is that the PPC 601 has instructions from the POWER (aka RS6000) ISA (mainly the
ones which set the mq special register which does not exist in PPC ISA) but that difference should not
make a difference if you are running on a true 601 unless the Linux kernel disables the POWER
compatiablity instructions.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=14053
next prev parent reply other threads:[~2004-02-20 21:51 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-06 23:02 [Bug c/14053] New: " stefaan dot simoens at tiscali dot be
2004-02-07 2:31 ` [Bug c/14053] " pinskia at gcc dot gnu dot org
2004-02-10 1:36 ` [Bug optimization/14053] " pinskia at gcc dot gnu dot org
2004-02-13 17:30 ` stefaan dot simoens at tiscali dot be
2004-02-13 17:31 ` stefaan dot simoens at tiscali dot be
2004-02-13 17:32 ` stefaan dot simoens at tiscali dot be
2004-02-13 17:33 ` stefaan dot simoens at tiscali dot be
2004-02-13 17:49 ` stefaan dot simoens at tiscali dot be
2004-02-20 21:12 ` stefaan dot simoens at tiscali dot be
2004-02-20 21:51 ` pinskia at gcc dot gnu dot org [this message]
2004-02-20 22:03 ` geoffk at geoffk dot org
2004-02-21 2:00 ` stefaan dot simoens at tiscali dot be
2004-02-25 11:05 ` stefaan dot simoens at tiscali dot be
2004-05-12 12:00 ` stefaan dot simoens at tiscali dot be
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=20040220215113.3399.qmail@sources.redhat.com \
--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).