From: Andreas Schwab <schwab@linux-m68k.org>
To: Segher Boessenkool <segher@kernel.crashing.org>
Cc: gcc-patches@gcc.gnu.org, dje.gcc@gmail.com
Subject: Re: [PATCH] rs6000: Set rs6000_cpu correctly (PR43871)
Date: Sat, 02 Dec 2017 18:56:00 -0000 [thread overview]
Message-ID: <87y3mluffz.fsf@linux-m68k.org> (raw)
In-Reply-To: <b2b3437da934358d760b13c58ae83939374aad1a.1512058731.git.segher@kernel.crashing.org> (Segher Boessenkool's message of "Thu, 30 Nov 2017 16:21:59 +0000")
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
Andreas.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
next prev parent reply other threads:[~2017-12-02 18:56 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 [this message]
2017-12-02 22:41 ` David Edelsohn
2017-12-02 22:53 ` Segher Boessenkool
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=87y3mluffz.fsf@linux-m68k.org \
--to=schwab@linux-m68k.org \
--cc=dje.gcc@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=segher@kernel.crashing.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).