From: Keith Packard <keithp@keithp.com>
To: Kito Cheng <kito.cheng@gmail.com>
Cc: Andrew Pinski <pinskia@gmail.com>, GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH 0/3] picolibc: Add picolibc linking help
Date: Thu, 25 Aug 2022 10:38:14 -0700 [thread overview]
Message-ID: <87v8qg8bqx.fsf@keithp.com> (raw)
In-Reply-To: <CA+yXCZCzx=M_Ei8-BDA1Z4nnHLkqKzPMpntVLVy=xwRmHtqnhQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 829 bytes --]
Kito Cheng <kito.cheng@gmail.com> writes:
> I am thinking that maybe we should add
> -mlibc=[newlib|newlib-nano|picolibc|unknown] option to bare-matel
> toolchain, one reason is having an unify interface to select libc
> implementation between clang/LLVM, spec file is a GCC specific stuff,
> that cause very bad compatibility between GCC and clang/LLVM, and
> having option to control that would be better since clang/LLVM don't
> have those configure time option.
You can create specs file for each library so that you select the
library with --specs=picolibc.specs or --specs=newlib-nano.specs. That
seems sufficient as you can mess with various compiler options and set
the header paths. Crosstool-ng does this and it enables delivering
newlib, newlib-nano and picolibc in the same toolchain.
--
-keith
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next prev parent reply other threads:[~2022-08-25 17:38 UTC|newest]
Thread overview: 19+ 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 ` [PATCH 0/3] picolibc: Add picolibc linking help Andrew Pinski
2022-08-24 19:32 ` Keith Packard
2022-08-25 7:16 ` Kito Cheng
2022-08-25 17:38 ` Keith Packard [this message]
2022-09-02 12:36 ` Richard Sandiford
2022-09-03 6:02 ` Keith Packard
2022-09-03 6:07 ` Keith Packard
2022-09-03 6:07 ` [PATCH 1/3] Allow default libc to be specified to configure Keith Packard
2022-09-03 6:07 ` [PATCH 2/3] Add newlib and picolibc as default C library choices Keith Packard
2022-09-03 6:07 ` [PATCH 3/3] Add '--oslib=' option when default C library is picolibc Keith Packard
2022-11-21 7:11 ` Sebastian Huber
2023-02-05 7:10 ` [PATCH 0/3] picolibc: Add picolibc linking help (v3) Keith Packard
2023-02-05 7:10 ` [PATCH 1/3] Allow default libc to be specified to configure Keith Packard
2023-02-05 7:10 ` [PATCH 2/3] Add newlib and picolibc as default C library choices Keith Packard
2023-02-05 7:10 ` [PATCH 3/3] Add '--oslib=' option when default C library is picolibc 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=87v8qg8bqx.fsf@keithp.com \
--to=keithp@keithp.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=kito.cheng@gmail.com \
--cc=pinskia@gmail.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).