public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Aldy Hernandez <aldyh@romulus-int.sfbay.redhat.com>
To: aldyh@sources.redhat.com
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: bootstrap/9361: [powerpc-linux] GCC 3.2.1 Boostrap stage 2 compile error (corrections)
Date: Thu, 27 Feb 2003 19:46:00 -0000	[thread overview]
Message-ID: <20030227194601.12706.qmail@sources.redhat.com> (raw)

The following reply was made to PR bootstrap/9361; it has been noted by GNATS.

From: Aldy Hernandez <aldyh@romulus-int.sfbay.redhat.com>
To: dje@gcc.gnu.org, aldyh@sources.redhat.com, gcc-bugs@gcc.gnu.org,
   gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org, tfinneid@ifi.uio.no,
   gcc-gnats@gcc.gnu.org
Cc:  
Subject: Re: bootstrap/9361: [powerpc-linux] GCC 3.2.1 Boostrap stage 2 compile error (corrections)
Date: Thu, 27 Feb 2003 11:42:52 -0800

 On Thu, Feb 27, 2003 at 06:59:06PM -0000, dje@gcc.gnu.org wrote:
 > Synopsis: [powerpc-linux] GCC 3.2.1 Boostrap stage 2 compile error (corrections)
 
 Hi Thomas.
 
 In your message you specify that you are bootstrapping on a PowerBook G3,
 and that you are getting an "illegal instruction" error.  The G3 does not
 have AltiVec so, this seems like a sensible error message ;-).
 
 If you wish to bootstrap a native PPC compiler that will run on your G3,
 but generate code for AltiVec, just bootstrap with powerpc-linux-gnu
 and then use the following flags when compiling a program:
 
 	-mabi=altivec -maltivec
 
 Obviously, this program will not run on your G3.
 
 Can you close this PR?
 
 Aldy


             reply	other threads:[~2003-02-27 19:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-27 19:46 Aldy Hernandez [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-02-27 19:45 dje
2003-02-27 18:59 dje

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=20030227194601.12706.qmail@sources.redhat.com \
    --to=aldyh@romulus-int.sfbay.redhat.com \
    --cc=aldyh@sources.redhat.com \
    --cc=gcc-prs@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).