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]

Re: Urgent: bug fixes needed for GCC 3.0.2


    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.


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