public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Tobias Burnus <tobias@codesourcery.com>
To: Gerald Pfeifer <gerald@pfeifer.com>
Cc: gcc-patches <gcc-patches@gcc.gnu.org>,
	"Tom de Vries" <tdevries@suse.de>,
	"Thomas Schwinge" <thomas@codesourcery.com>,
	"Martin Liška" <mliska@suse.cz>,
	"Matthias Klose" <doko@ubuntu.com>
Subject: Re: [Patch] install.texi: Bump newlib version for nvptx + gcn
Date: Mon, 23 Jan 2023 10:30:05 +0100	[thread overview]
Message-ID: <f1f8be73-bbfa-ca4d-c949-621b704eca68@codesourcery.com> (raw)
In-Reply-To: <13b420c5-f19c-016c-3fbb-b3df6532962b@pfeifer.com>


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

  reply	other threads:[~2023-01-23  9:30 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-21  9:57 Tobias Burnus
2023-01-21 11:58 ` Gerald Pfeifer
2023-01-21 13:27   ` Tobias Burnus
2023-01-22  1:45     ` Gerald Pfeifer
2023-01-23  9:30       ` Tobias Burnus [this message]
2023-01-23 11:37         ` [wwwdocs] gcc-6: Consistently lower-case newlib (was: [Patch] install.texi: Bump newlib version for nvptx + gcn) Gerald Pfeifer

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=f1f8be73-bbfa-ca4d-c949-621b704eca68@codesourcery.com \
    --to=tobias@codesourcery.com \
    --cc=doko@ubuntu.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=gerald@pfeifer.com \
    --cc=mliska@suse.cz \
    --cc=tdevries@suse.de \
    --cc=thomas@codesourcery.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).