Re: CVS commit: src/sys/arch/macppc/stand/bootxx

[Valery Ushakov <uwe%stderr.spb.ru@localhost>]

On Sun, Mar 04, 2018 at 09:06:08 +1100, matthew green wrote:

> > On 03/03/18 02:06, matthew green wrote:
> > > you didn't grep enough :-)  eg:
> > > 
> > > dist/gcc/config/rs6000/rs6000.c:        prefix = (sel & SAVRES_SAVE) ? "_savegpr_" : "_restgpr_";
> > > 
> > > is the part that matters.
> > 
> > Just so I understand, where does this come into play from the bootxx
> > side, reason I ask is there is no noise in the build output. bootxx
> > compiles without warnings or complaint (I haven't touched the verbosity
> > settings). Would problems with this binary be expected on execution &
> > not during build?
> 
> i don't know.  i didn't actually look too deeply at it, but
> i did recall these functions are prefix+name generated.
> 
> we occasionally have to deal with this and either link against
> libgcc or provide them in libkern/libsa.  there can be new
> things from newer compilers, etc., when it starts emitting
> new calls it expects in libgcc or other.  kernels should not
> be using libgcc.

Right, I had to add a few things to libkern when gcc started emiting
new "millicode" for sh3 (only with certain gcc -m/-O options).

-uwe