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: MEM_COPY_ATTRIBUTES


    Reasonable argument.  But, volatility is a conservative choice;
    readonly-ness is an optimistic choice.

But the structure and scalar attributes that are moved are also an
optimistic choice.

    It's certainly not safe if the new MEM is bigger than the old one.

Sure, but when would you do that?  I can't think of any time that such
a thing would be done.

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