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

Re: gcc 3.4 regression: sched2 moving "may throw" instructions into epilogue


Andrew Haley <aph@redhat.com> writes:

| Jim Wilson writes:
|  > Andrew Haley wrote:
|  > > Is that right, though?  It's only trapping instructions that mustn't
|  > > be moved into the epilogue, not all instructions.  This solution
|  > > sounds like it would be an all-round performance loser.
|  > 
|  > I don't see any obvious way to restrict this to only trapping insns.
| 
| Well, there seem to be a number of places where this blockage insn
| could be emitted, and I can't decide which would be the best.  It
| could either be the start of the epilogue or the end of the funtion
| proper.  This is my best guess.
| 
| OK for mainline and branches?

OK for gcc-3_3-branch is favorably reviewed.

-- Gaby


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