This is the mail archive of the
mailing list for the GCC project.
Re: Urgent: bug fixes needed for GCC 3.0.2
- To: jakub at redhat dot com
- Subject: Re: Urgent: bug fixes needed for GCC 3.0.2
- From: kenner at vlsi1 dot ultra dot nyu dot edu (Richard Kenner)
- Date: Thu, 4 Oct 01 12:50:25 EDT
- Cc: gcc at gcc dot gnu dot org
I'm using following patch for this in gcc-2.96-RH (which Richard Kenner did
not like but it certainly is less invasive change then ignoring
RTX_UNCHANGING_P with sibling call optimization). IMHO clearing
RTX_UNCHANGING_P is a safe thing to do even if it cleared some innocent
variable's (which would be sharing the same stack slot) RTX_UNCHANGING_P
flag as opposed to setting it.
No. Neither setting of RTX_UNCHANGING_P is "safe". It must be
exactly correct. If it's turned off when it should be on, then a use
of that MEM will not conflict with one with RTX_UNCHANGING_P set.