This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug middle-end/49721] convert_memory_address_addr_space may generate invalid new insns
- From: "ubizjak at gmail dot com" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Wed, 3 Aug 2011 06:41:04 +0000
- Subject: [Bug middle-end/49721] convert_memory_address_addr_space may generate invalid new insns
- Auto-submitted: auto-generated
- References: <bug-49721-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49721
--- Comment #18 from Uros Bizjak <ubizjak at gmail dot com> 2011-08-03 06:40:45 UTC ---
(In reply to comment #17)
> H.J., I agree with what you write in comment 16. But unless we are sure that
> the problematic composition will never be generated (e.g. by ivopts), we cannot
> afford that.
>
> The patch in comment 7 may have some snafu, but overall it looks very sane.
> It's just that a const is not being stripped. Can it be applied on top of the
> x32 branch? Or do I first have to revert some earlier revision?
The patch can be applied to current trunk as-is and all the problems discussed
here will be shown by simply compiling with -mx32.