This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug target/52698] -maddress-mode=long doesn't work
- From: "ubizjak at gmail dot com" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Sun, 25 Mar 2012 22:28:23 +0000
- Subject: [Bug target/52698] -maddress-mode=long doesn't work
- Auto-submitted: auto-generated
- References: <bug-52698-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52698
Uros Bizjak <ubizjak at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Attachment #26974|0 |1
is obsolete| |
--- Comment #5 from Uros Bizjak <ubizjak at gmail dot com> 2012-03-25 22:28:23 UTC ---
Created attachment 26987
--> http://gcc.gnu.org/bugzilla/attachment.cgi?id=26987
Patch that teaches x86 how to fix invalid reload address
Attached patch teaches x86 how to fix invalid reload address.
However, I'd say that there is a problem within reload pass, where reload
creates partially reloaded address, comprising strict and non-strict registers
(see comment #4). This address is passed to ix86_legitimate_address_p in strict
mode, and gets rejected. Reload then bravely pushes every component into a
separate registers (3 in this case). This action creates even more invalid
address, also violating #define MAX_REGS_PER_ADDRESS 2.