Re: Compiling libgcc functions with non-default LIBGCC2_UNITS_PER_WORD

2007-01-21 Thread Daniel Jacobowitz
On Sun, Jan 21, 2007 at 11:09:56PM +0100, Rask Ingemann Lambertsen wrote: >I would like to be able to add something like > > LIBGCC2_EXTRA_FUNCS = _ashldi3:2 _ashrdi3:2 _lshrdi3:2 _divdi3:2 _moddi3:2 > > to t-machine instead of > > LIB2FUNCS_EXTRA = ashlsi3.c ashrsi3.c lshrsi3.c ... > > ash

Re: Compiling libgcc functions with non-default LIBGCC2_UNITS_PER_WORD

2007-01-21 Thread Rask Ingemann Lambertsen
On Sun, Jan 21, 2007 at 02:00:06PM -0500, Daniel Jacobowitz wrote: > On Sat, Jan 20, 2007 at 01:15:19PM +0100, Rask Ingemann Lambertsen wrote: > >Somewhere in the libgcc build machinery, there is mechanism to override > > the default LIBGCC2_UNITS_PER_WORD setting when compilng a function, so y

Re: Compiling libgcc functions with non-default LIBGCC2_UNITS_PER_WORD

2007-01-21 Thread Daniel Jacobowitz
On Sat, Jan 20, 2007 at 01:15:19PM +0100, Rask Ingemann Lambertsen wrote: >Somewhere in the libgcc build machinery, there is mechanism to override > the default LIBGCC2_UNITS_PER_WORD setting when compilng a function, so you > could in principle provide e.g. _divsi3 as well as _divdi3. It there

Compiling libgcc functions with non-default LIBGCC2_UNITS_PER_WORD

2007-01-20 Thread Rask Ingemann Lambertsen
Somewhere in the libgcc build machinery, there is mechanism to override the default LIBGCC2_UNITS_PER_WORD setting when compilng a function, so you could in principle provide e.g. _divsi3 as well as _divdi3. It there a way of making use of this facility in a more elegant way than putting the who