From: Segher Boessenkool <segher@kernel.crashing.org>
To: David Edelsohn <dje.gcc@gmail.com>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>,
Andreas Schwab <schwab@linux-m68k.org>
Subject: Re: [PATCH] rs6000: Set rs6000_cpu correctly (PR43871)
Date: Sat, 02 Dec 2017 22:53:00 -0000 [thread overview]
Message-ID: <20171202225257.GP10515@gate.crashing.org> (raw)
In-Reply-To: <CAGWvnynQepGGV8P0BRWTqcnyX8m5y+R+wVn50SJ61zNnRs6qJQ@mail.gmail.com>
On Sat, Dec 02, 2017 at 05:41:20PM -0500, David Edelsohn wrote:
> On Sat, Dec 2, 2017 at 1:56 PM, Andreas Schwab <schwab@linux-m68k.org> wrote:
> > configured by ../configure, generated by GNU Autoconf 2.64,
> > with options " '--prefix=/usr' '--build=powerpc64-suse-linux' '--enable-checking=release' '--enable-shared' 'CFLAGS=-O2 -g' 'CXXFLAGS=-O2 -g' '--with-cpu-64=power4' '--enable-secureplt' '--with-long-double-128' '--with-system-zlib' '--disable-bootstrap' 'build_alias=powerpc64-suse-linux' '--enable-languages=c,lto'"
> >
> > configure:3475: /daten/gcc/test/Build/./gcc/xgcc -B/daten/gcc/test/Build/./gcc/ -B/usr/powerpc64-suse-linux/bin/ -B/usr/powerpc64-suse-linux/lib/ -isystem /usr/powerpc64-suse-linux/include -isystem /usr/powerpc64-suse-linux/sys-include -m32 -o conftest -O2 -g conftest.c >&5
> > cc1: internal compiler error: in rs6000_option_override_internal, at config/rs6000/rs6000.c:4187
> > 0x10a8fdab rs6000_option_override_internal
> > ../../gcc/config/rs6000/rs6000.c:4187
> > 0x1017460b process_options
> > ../../gcc/toplev.c:1234
> > 0x1017460b do_compile
> > ../../gcc/toplev.c:2015
>
>
> This broke bootstrap on AIX similarly.
It was too good to be true, a simple two-liner would solve this, heh.
I think I know what to do (needs testing, will be tomorrow at earliest);
but deeper investigation shows we use rs6000_cpu in quite a few places
where we mean rs6000_tune (which doesn't exist). I don't know how deep
this pit is. Feel free to revert my patch (if it takes too long to fix
this, I'll revert it myself).
Sorry :-/
Segher
prev parent reply other threads:[~2017-12-02 22:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-30 16:32 Segher Boessenkool
2017-12-02 18:56 ` Andreas Schwab
2017-12-02 22:41 ` David Edelsohn
2017-12-02 22:53 ` Segher Boessenkool [this message]
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=20171202225257.GP10515@gate.crashing.org \
--to=segher@kernel.crashing.org \
--cc=dje.gcc@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=schwab@linux-m68k.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).