public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "segher at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/53266] Error: Unrecognized opcode: `mulhwu'
Date: Tue, 25 Sep 2012 11:45:00 -0000	[thread overview]
Message-ID: <bug-53266-4-CYqFRZyX6A@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-53266-4@http.gcc.gnu.org/bugzilla/>


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

--- Comment #5 from Segher Boessenkool <segher at gcc dot gnu.org> 2012-09-25 11:44:42 UTC ---
> I haven't built GCC on the AIX 4.3 (PowerPC 604) system lately, but my scripts
> are set up to do so using
> 
>     --with-cpu=powerpc --disable-aix64 --disable-powercpu
> 
> in order to avoid this issue. Should I be able to drop any of these, at this
> point?

You can remove the --with-cpu; the default on AIX4.3 is 604e,
which should work fine.  I don't think you can yet remove the
--disable-powercpu since I didn't touch the multilib code (I
completely missed it, and wow it's a nice little maze all of
itself).  I have no idea about --disable-aix64.  Try and see :-)


  parent reply	other threads:[~2012-09-25 11:45 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-07 14:31 [Bug bootstrap/53266] New: " skunk at iskunk dot org
2012-05-07 17:43 ` [Bug bootstrap/53266] " pinskia at gcc dot gnu.org
2012-05-07 17:45 ` skunk at iskunk dot org
2012-09-25  7:31 ` segher at gcc dot gnu.org
2012-09-25 10:57 ` skunk at iskunk dot org
2012-09-25 11:45 ` segher at gcc dot gnu.org [this message]
2012-09-25 21:38 ` skunk at iskunk dot org
2012-09-26  5:49 ` segher at gcc dot gnu.org
2012-09-26  6:06 ` skunk at iskunk dot org
2012-09-26  6:44 ` segher at gcc dot gnu.org
2012-09-27 14:02 ` skunk at iskunk dot org
2021-07-19  7:13 ` pinskia at gcc dot gnu.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=bug-53266-4-CYqFRZyX6A@http.gcc.gnu.org/bugzilla/ \
    --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).