On 22.01.23 02:45, Gerald Pfeifer wrote:
Maybe, but the question is what to use? The project's webpage has on the
first page: "patch submissions to Newlib" and "automate the testing of
newlib".
I also dug into the newlib web page and other sources and - while my
personal preference slightly leans towards Newlib - believe newlib is
more established overall.
For the web pages, it's clearer than for our *.texi ones you dug into:
~/src/wwwdocs/htdocs> grep -r newlib . | wc -l
15
~/src/wwwdocs/htdocs> grep -r Newlib . | wc -l
3
You need to be careful with those counts as there is not only 'the [nN]ewlib
library'
but also flags/configure arguments etc:
gcc/doc/install.texi:@item --with-newlib
gcc/doc/install.texi-@item --with-nds32-lib=@var{library}
gcc/doc/install.texi:Currently, the valid @var{library} is @samp{newlib} or
@samp{mculib}.
gcc/doc/install.texi:to nvptx-newlib's @file{newlib} directory to the directory
containing
gcc/doc/install.texi:@option{--enable-newlib-io-long-long} options when
configuring.
gcc/doc/invoke.texi:@samp{--enable-newlib-nano-formatted-io}.
gcc/doc/invoke.texi:@item -mnewlib
gcc/doc/invoke.texi:@opindex mnewlib
(and a few more).
In the libstdc++-v3/doc/xml/, there are two 'newlib' and one 'Newlib'
(plus a bunch of newlib as filename/argument/config option).
Still, I concur that 'newlib' is still used a bit more often than 'Newlib'.
* * *
In any case, I concur that it would be nice to unify .texi/.xml and diagnostic
output (twice in config/or1k/elf.opt) - and likewise the wwwdocs pages.
(That elf.opt file has twice 'newlib' and once 'Newlib'.)
-> adds this to the to-do list.
Tobias
-----------------
Siemens Electronic Design Automation GmbH; Anschrift: Arnulfstraße 201, 80634
München; Gesellschaft mit beschränkter Haftung; Geschäftsführer: Thomas
Heurung, Frank Thürauf; Sitz der Gesellschaft: München; Registergericht
München, HRB 106955
