This is the mail archive of the gcc-patches@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]

Re: fix for explicit SET modes


   Date: Fri, 14 Aug 1998 09:29:06 -0600
   From: Jeffrey A Law <law@hurl.cygnus.com>

   This is definitely wrong for the PA.

This is why I sent the patch out for scurtiny :-)

   The DImode is used to distinguish between two patterns which have the
   same RTL form (a simple jump), but which must have different code at
   assembly time because one appears inside a jump table.

   We can certainly look for another way to solve the PA specific issue,
   but first I want to know exactly why this is important.

If reload sees a SET that happens to be in DImode, it does funny stuff
like marking destination registers dead at all such DImode SETs etc.

I saw this because I had some bugs in my sparc64 constant formation
code which set DImode on the SETs by accident, the result was improper
REG_DEAD notes all over the place after reload.

Just stick an unspec in there for this PA case...

Later,
David S. Miller
davem@dm.cobaltmicro.com


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