Re: [avr-libc-dev] Bugs before 1.2.0

[Paul Schlie]

>> (also, not sure what was meant by "merge" libc and libm, but they
>> logically should remain distinct.)
>> 
> Simple. Merge them into one libc.a library.
> 
> Please give a good reason why you think they should remain distinct.
> What advantages would there be for keeping them seperate?

Possibly because they are distinct collections of functions, for distinct
purposes, which are traditionally presumed to be and utilized as such.
(which would then also help simplify make files which may use avr-libc
or other equivalent traditional C libraries more or less interchangeably;
which will become more significant as avr-libc efforts are hopefully
unified with those in support of an avr newlib effort).

(If you want to merge these distinct libraries into a single linkable
dead-code-strip-able library, it shouldn't likely be named libc, as
that's not what C programmers would expect it to contain.)