public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "krebbel at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/48353] New: Bootstrap fail due to invalid register pair being assigned to pseudo
Date: Wed, 30 Mar 2011 07:18:00 -0000 [thread overview]
Message-ID: <bug-48353-4@http.gcc.gnu.org/bugzilla/> (raw)
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48353
Summary: Bootstrap fail due to invalid register pair being
assigned to pseudo
Product: gcc
Version: 4.7.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: middle-end
AssignedTo: unassigned@gcc.gnu.org
ReportedBy: krebbel@gcc.gnu.org
Created attachment 23811
--> http://gcc.gnu.org/bugzilla/attachment.cgi?id=23811
testcase
Compiling the attached testcase with -O2 produces an invalid divide
instruction:
dsgfr %r7,%r1
The first parameter needs to an even numbered register.
from ira dump:
Try Assign 103(a10), cost=226: reassign to 7
changing reg in insn 50
Register 93 now in 3.
Register 103 now in 7.
(insn 50 40 62 4 (set (reg:TI 7 %r7 [103])
(ior:TI (ashift:TI (zero_extend:TI (mod:DI (reg:DI 8 %r8 [99])
(sign_extend:DI (reg/v:SI 1 %r1 [orig:49 copy_nregs ]
[49]))))
(const_int 64 [0x40]))
(zero_extend:TI (div:DI (reg:DI 8 %r8 [99])
(sign_extend:DI (reg/v:SI 1 %r1 [orig:49 copy_nregs ]
[49])))))) t.c:32 380 {divmodtisi3}
(nil))
next reply other threads:[~2011-03-30 6:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-30 7:18 krebbel at gcc dot gnu.org [this message]
2011-03-30 7:25 ` [Bug middle-end/48353] " krebbel at gcc dot gnu.org
2011-03-30 7:29 ` krebbel at gcc dot gnu.org
2011-03-30 9:26 ` [Bug middle-end/48353] [4.7 Regression] " rguenth at gcc dot gnu.org
2011-03-30 14:53 ` krebbel 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-48353-4@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).