From: Andrew Pinski <pinskia@gmail.com>
To: Keith Packard <keithp@keithp.com>
Cc: gcc@gcc.gnu.org, gcc-patches@gcc.gnu.org
Subject: Re: [PATCH 0/3] picolibc: Add picolibc linking help
Date: Wed, 24 Aug 2022 11:24:12 -0700 [thread overview]
Message-ID: <CA+=Sn1na1cxxzhD_zjAnYN97j2hMhChNPi8b8BUTtLXKMNGRhw@mail.gmail.com> (raw)
In-Reply-To: <20220824180426.820576-1-keithp@keithp.com>
On Wed, Aug 24, 2022 at 11:12 AM Keith Packard via Gcc-patches
<gcc-patches@gcc.gnu.org> wrote:
>
> Picolibc is a C library for embedded systems based on code from newlib
> and avr libc. To connect some system-dependent picolibc functions
> (like stdio) to an underlying platform, the platform may provide an OS
> library.
>
> This OS library must follow the C library in the link command line. In
> current picolibc, that is done by providing an alternate .specs file
> which can rewrite the *lib spec to insert the OS library in the right
> spot.
Why do you need to change the specs to support picolibc? Why not have
the library supply the specs file instead, like what is done for
newlib and libgloss?
>
> This patch series adds the ability to specify the OS library on the
> gcc command line when GCC is configured to us picolibc as the default
> C library, and then hooks that up for arm, nds32, riscv and sh targets.
What OS libraries are not included in libc? I trying to figure out why
this needs to be special cased here.
Thanks,
Andrew Pinski
>
> Keith Packard (3):
> Allow default libc to be specified to configure
> Add newlib and picolibc as default C library choices
> Add '--oslib=' option when default C library is picolibc
>
> gcc/config.gcc | 56 ++++++++++++++++++++++++++++++++-------
> gcc/config/arm/elf.h | 5 ++++
> gcc/config/nds32/elf.h | 4 +++
> gcc/config/picolibc.opt | 26 ++++++++++++++++++
> gcc/config/riscv/elf.h | 4 +++
> gcc/config/sh/embed-elf.h | 5 ++++
> gcc/configure.ac | 4 +++
> 7 files changed, 95 insertions(+), 9 deletions(-)
> create mode 100644 gcc/config/picolibc.opt
>
> --
> 2.36.1
>
next prev parent reply other threads:[~2022-08-24 18:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-24 18:04 Keith Packard
2022-08-24 18:04 ` [PATCH 1/3] picolibc: Allow default libc to be specified to configure Keith Packard
2022-08-24 18:04 ` [PATCH 2/3] picolibc: Add newlib and picolibc as default C library choices Keith Packard
2022-08-24 18:04 ` [PATCH 3/3] picolibc: Add '--oslib=' option when default C library is picolibc Keith Packard
2022-08-24 18:24 ` Andrew Pinski [this message]
2022-09-02 12:36 ` [PATCH 0/3] picolibc: Add picolibc linking help Richard Sandiford
2022-09-03 6:02 ` Keith Packard
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='CA+=Sn1na1cxxzhD_zjAnYN97j2hMhChNPi8b8BUTtLXKMNGRhw@mail.gmail.com' \
--to=pinskia@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gcc@gcc.gnu.org \
--cc=keithp@keithp.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).