GSOC:disable newlibc reentrancy

[Ralf Corsepius]

On Thu, 2008-05-08 at 08:27 -0500, Joel Sherrill wrote:
> Ralf Corsepius wrote:
> > On Thu, 2008-05-08 at 20:35 +0800, 阎淼 wrote:
> >   
> >> 2008/5/8, Ralf Corsepius <ralf.corsepius at rtems.org>:
> >>     
> >>> On Thu, 2008-05-08 at 15:26 +0800, 阎淼 wrote:
> >>>       
> >>>> 2008/5/8, Ralf Corsepius <ralf.corsepius at rtems.org>:
> >>>>         
> >>>>> On Thu, 2008-05-08 at 14:54 +0800, 阎淼 wrote:
> >>>>>           
> >>>>>> Hi,
> >>>>>>
> >>>>>> I am trying to disable newlibc.c reentrant support.
> >>>>>>             
> >>>>> Why do you want to do this?
> >>>>>           
> >>>> That is one of the size reduction ideas of tiny rtems project.
> >>>>         
> >>> OK, in verbose: What you are doing is absurd. It means to cut-off rtems
> >>> from newlib, turning all of newlib and the whole compiler unusable.
> >>>
> >>>       
> >>    What is your suggestion?  And if newlibc reentrant extensions are
> >> not supposed to be an option,  why macro like
> >> CONFIGURE_DISABLE_NEWLIB_REENTRANCY exists in confdefs.h ?
> >>     
> > Because somebody didn't switch on his brains.
> >
> > Switching off reentrancy means using a different ABI inside of RTEMS
> > than the toolchain's libc.
> >
> >   
> No it doesn't.  It simply means that all threads share a
> single reentrancy structure.  No calls break.
> > It means abusing the toolchain for a different compiler target.
> >
> >   
> No it doesn't.  It is turning off a run-time feature.

Not in gcc/newlib

Ralf