Re: patch for prologue/epilogue generation

[Gunther Nikl <gni at gecko dot de>]

On Sat, Aug 23, 2003 at 12:01:54AM +0200, Bernardo Innocenti wrote:
> I'd like to go one step further and just call m68k_compute_frame_layout()
> once per function, storing the result somewhere to reuse it later in all of
> m68k_initial_elimination_offset() and m68k_output_function_{pro|epi}logue().

  If thats possible, then its probably an improvement.
  I just noticed that m68k_compute_frame_layout has an if (0) block with
  a commented TARGET_CFV4E. Is that block necessary? The only difference
  with the TARGET_68881 block is the multiplication factor to frame->offset.
  Would it be feasable to merge frame.offset and frame.size? AFAICS, both
  are always returned added together in m68k_initial_elimination_offset.
  Note, the patch has to be updated again since the ISO C90 conversion has
  probably broken it. Finally, in an added comment to m68k.h i386 is named.

> Could you please build this test program to check if C++ exceptions are
> still working correctly on m68k? (It's attached). It doesn't work on
> ColdFire.

  I could but the AmigaOS port doesn't use DWARF2. Can an a.out target use
  it?

> >   I have no idea how to run the GCC testsuite let alone whether this
> >   would work on my non-unix m68k system.
> 
> The testsuite is very simple to use if you already have expect and dejagnu
> installed. Once you have these in place, you just need to do "make test" to
> build and (sometimes) run thousands of small tests covering almost every
> feature of GCC.

  I will take a look.

  Gunther