This is the mail archive of the libc-ports@sources.redhat.com mailing list for the libc-ports 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: Ping Re: PowerPC E500 port


> Different trade-offs are appropriate for users of different C libraries; 
> newlib and uClibc use a different implementation that's smaller but less 
> accurate.  Existing practice regarding ABI-specified functions when they 
> aren't of the nature of functions generally included in libgcc puts them 
> in libc (e.g., the ARM EABI functions in glibc).

Ok, I don't much care for an obscure port.  
I would not repeat that mistake the future, however.
New machine-independent user interfaces belong in separate libraries.

> Existing practice with users of this code has both the GLIBC_2.3.3 and 
> GLIBC_2.5 symbols.  Existing practice for development of new ports is to 
> develop the code (using versions current at that time) and get it in use 
> among users of that hardware, then merge in with the same symbol versions 
> as are in use in the field (so ColdFire was merged with GLIBC_2.4 version 
> although that merge was just after 2.5 branched).

Ok.


Thanks,
Roland


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