This is the mail archive of the gcc-bugs@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Bug target/27234] no way to stop gcc from mucking with the incoming argument stack on ia32



------- Comment #20 from hubicka at gcc dot gnu dot org  2008-04-29 15:40 -------
Created an attachment (id=15546)
 --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=15546&action=view)
New patch

Hi,
this patch implements idea of having temporary read-only register with
REG_EQUIV note that will get propagated to place of the read-write parameter
register.
However I am still midly confused, when reload is actually using the operand
slot in read-write way?  I don't seem to be able to construct a testcase.
If reload is not doing that, perhaps just dropping the function.c part of patch
is easiest way around.

Honza


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=27234


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]