public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "fxcoudert at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/63703] [4.9.2 Regression] cc1: internal compiler error: in init_reg_sets, at reginfo.c:178
Date: Sun, 23 Nov 2014 17:36:00 -0000 [thread overview]
Message-ID: <bug-63703-4-ffnjEMOvtp@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-63703-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63703
Francois-Xavier Coudert <fxcoudert at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Last reconfirmed|2014-11-22 00:00:00 |2014-11-23
CC| |edmarwjr at gcc dot gnu.org,
| |rohitarulraj at gmail dot com
--- Comment #8 from Francois-Xavier Coudert <fxcoudert at gcc dot gnu.org> ---
I've reproduced this with a cross-compiler targeting powerpc-apple-darwin9: the
cc1 built fails at startup, with any source file, as shown above.
Then bisection shows this 4.9.2 regression is due to revision 213597:
2014-08-04 Rohit <rohitarulraj@freescale.com>
* config/rs6000/rs6000.c
(rs6000_reg_names) : Add SPE high register names.
(alt_reg_names) : Likewise.
(rs6000_dwarf_register_span) : For SPE high registers, replace
dwarf register numbers with GCC hard register numbers.
(rs6000_init_dwarf_reg_sizes_extra) : Likewise.
(rs6000_dbx_register_number): For SPE high registers, return dwarf
register number for the corresponding GCC hard register number.
* config/rs6000/rs6000.h
(FIRST_PSEUDO_REGISTER) : Update based on 32 newly added GCC hard
register numbers for SPE high registers.
(DWARF_FRAME_REGISTERS) : Likewise.
(DWARF_REG_TO_UNWIND_COLUMN) : Likewise.
(DWARF_FRAME_REGNUM) : Likewise.
(FIXED_REGISTERS) : Likewise.
(CALL_USED_REGISTERS) : Likewise.
(CALL_REALLY_USED_REGISTERS) : Likewise.
(REG_ALLOC_ORDER) : Likewise.
(enum reg_class) : Likewise.
(REG_CLASS_NAMES) : Likewise.
(REG_CLASS_CONTENTS) : Likewise.
(SPE_HIGH_REGNO_P) : New macro to identify SPE high registers.
I looked into reginfo.c: array initial_reg_names has 117 elements:
static const char *const initial_reg_names[] = { "r0", "r1", "r2", "r3", "r4",
"r5", "r6", "r7", "r8", "r9", "r10", "r11", "r12", "r13", "r14", "r15", "r16",
"r17", "r18", "r19", "r20", "r21", "r22", "r23", "r24", "r25", "r26", "r27",
"r28", "r29", "r30", "r31", "f0", "f1", "f2", "f3", "f4", "f5", "f6", "f7",
"f8", "f9", "f10", "f11", "f12", "f13", "f14", "f15", "f16", "f17", "f18",
"f19", "f20", "f21", "f22", "f23", "f24", "f25", "f26", "f27", "f28", "f29",
"f30", "f31", "mq", "lr", "ctr", "ap", "cr0", "cr1", "cr2", "cr3", "cr4",
"cr5", "cr6", "cr7", "xer", "v0", "v1", "v2", "v3", "v4", "v5", "v6", "v7",
"v8", "v9", "v10", "v11", "v12", "v13", "v14", "v15", "v16", "v17", "v18",
"v19", "v20", "v21", "v22", "v23", "v24", "v25", "v26", "v27", "v28", "v29",
"v30", "v31", "vrsave", "vscr", "spe_acc", "spefscr", "sfp", "tfhar", "tfiar",
"texasr" };
while reg_names (this_target_hard_regs->x_reg_names) has size
FIRST_PSEUDO_REGISTER, which equals 149.
next prev parent reply other threads:[~2014-11-23 17:36 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-31 18:38 [Bug bootstrap/63703] New: " dougmencken at gmail dot com
2014-10-31 18:39 ` [Bug bootstrap/63703] " dougmencken at gmail dot com
2014-10-31 18:47 ` dougmencken at gmail dot com
2014-10-31 19:20 ` dougmencken at gmail dot com
2014-11-03 9:17 ` [Bug bootstrap/63703] [4.9 " rguenth at gcc dot gnu.org
2014-11-03 9:17 ` rguenth at gcc dot gnu.org
2014-11-21 19:32 ` larryv at macports dot org
2014-11-22 16:54 ` [Bug bootstrap/63703] [4.9.2 " fxcoudert at gcc dot gnu.org
2014-11-23 16:31 ` gcc@Denis-Excoffier.org
2014-11-23 17:36 ` fxcoudert at gcc dot gnu.org [this message]
2014-11-23 17:43 ` [Bug bootstrap/63703] [4.9.2/5 Regression] Bootstrap broken on powerpc-apple-darwin, cc1: internal compiler error: in init_reg_sets fxcoudert at gcc dot gnu.org
2014-11-23 17:59 ` iains at gcc dot gnu.org
2014-11-23 18:07 ` fxcoudert at gcc dot gnu.org
2014-11-24 16:31 ` rohitarulraj at gmail dot com
2014-11-24 16:48 ` iains at gcc dot gnu.org
2014-11-24 19:07 ` rohitarulraj at gmail dot com
2014-11-25 6:23 ` misty at brew dot sh
2014-11-25 19:01 ` fxcoudert at gcc dot gnu.org
2014-11-25 21:42 ` fxcoudert at gcc dot gnu.org
2014-11-25 21:55 ` fxcoudert at gcc dot gnu.org
2014-11-26 3:22 ` larryv at macports dot org
2014-11-26 8:11 ` iains at gcc dot gnu.org
2014-11-27 5:47 ` gcc@Denis-Excoffier.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-63703-4-ffnjEMOvtp@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).