This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug middle-end/19304] [4.0 Regression] wrong code for spec test from emit_move_change_mode
- From: "rth at gcc dot gnu dot org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 13 Jan 2005 08:11:24 -0000
- Subject: [Bug middle-end/19304] [4.0 Regression] wrong code for spec test from emit_move_change_mode
- References: <20050106233743.19304.janis187@us.ibm.com>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Additional Comments From rth at gcc dot gnu dot org 2005-01-13 08:11 -------
My new code, so I'll own the bug. But I'm a bit confused by this. In what
sort of situation are we requiring the subreg built, and simplify_subreg is
rejecting the subreg as illegal?
Could you run the compiler with your patch, but instead of a call to
simplify_gen_subreg, call simplify_subreg (like below), but abort if it
returns NULL? And then see if it triggers within the gcc source tree or
something handy like that where it's legally easier to give me .i file?
If you can't find anything but spec to produce this, we'll work something
out, but I'm lazy and wanna try this the easy way first.
--
What |Removed |Added
----------------------------------------------------------------------------
AssignedTo|unassigned at gcc dot gnu |rth at gcc dot gnu dot org
|dot org |
Status|NEW |ASSIGNED
Last reconfirmed|2005-01-07 12:24:56 |2005-01-13 08:11:21
date| |
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19304