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: m68k bootstrapping broken


On Thu, Jan 08, 2004 at 10:58:31PM +0100, Bernardo Innocenti wrote:
> Richard Zidlicky wrote:
> 
> >The above diffs may suggest that something is wrong with the
> >improved prologue/epilogue generation on m68k but since this
> >is a miscompiled compiler it could be very easilly pure
> >coincidence.
> 
> A non-trivial side-effect of the new frame generation code
> is that, when -fomit-frame-pointer is enabled, there's no
> longer a wasted slot where the frame pointer would normally
> be saved.
> 
> This change could affect buggy user code containing
> off-by-one stack overflows.

Is it possible that there is some endianness or similar issue
inside the new frame generation code? Bitfields or whatever might
cause portability problems?

> IIRC, -O2 implies -fomit-frame-pointer on the m68k. 

it doesnt imply that. I have already tried both variants, no
visible difference wrt this bug.

Richard


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