[Bug middle-end/23868] [4.1/4.2 regression] builtin_apply uses wrong mode for multi-hard-register return values

2006-07-23 Thread echristo at apple dot com
--- Comment #8 from echristo at apple dot com 2006-07-24 05:45 --- Is this a problem with mainline? It has 4.2 regression marked on it. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=23868

[Bug middle-end/23868] [4.1/4.2 regression] builtin_apply uses wrong mode for multi-hard-register return values

2006-07-23 Thread pinskia at gcc dot gnu dot org
--- Comment #9 from pinskia at gcc dot gnu dot org 2006-07-24 05:51 --- (In reply to comment #8) Is this a problem with mainline? It has 4.2 regression marked on it. Why do you think otherwise, the commits were all to a developmental branch and the patch is up on the patch queue so why

[Bug middle-end/23868] [4.1/4.2 regression] builtin_apply uses wrong mode for multi-hard-register return values

2006-05-24 Thread mmitchel at gcc dot gnu dot org
--- Comment #7 from mmitchel at gcc dot gnu dot org 2006-05-25 02:33 --- Will not be fixed in 4.1.1; adjust target milestone to 4.1.2. -- mmitchel at gcc dot gnu dot org changed: What|Removed |Added

[Bug middle-end/23868] [4.1/4.2 regression] builtin_apply uses wrong mode for multi-hard-register return values

2006-02-23 Thread mmitchel at gcc dot gnu dot org
--- Comment #6 from mmitchel at gcc dot gnu dot org 2006-02-24 00:26 --- This issue will not be resolved in GCC 4.1.0; retargeted at GCC 4.1.1. -- mmitchel at gcc dot gnu dot org changed: What|Removed |Added

[Bug middle-end/23868] [4.1/4.2 regression] builtin_apply uses wrong mode for multi-hard-register return values

2006-02-17 Thread mmitchel at gcc dot gnu dot org
-- mmitchel at gcc dot gnu dot org changed: What|Removed |Added Priority|P3 |P2 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=23868

[Bug middle-end/23868] [4.1/4.2 regression] builtin_apply uses wrong mode for multi-hard-register return values

2006-02-16 Thread pinskia at gcc dot gnu dot org
--- Comment #5 from pinskia at gcc dot gnu dot org 2006-02-16 15:19 --- (In reply to comment #4) Mark, why isn't this marked as a regression? Most likey because I and others did not notice it was a regression and could not tell from either the patch or the bug report it was. --