From: Jonathan Wakely <jwakely@redhat.com>
To: Jason Merrill <jason@redhat.com>
Cc: gcc-patches@gcc.gnu.org, libstdc++@gcc.gnu.org
Subject: Re: [PATCH RFA] libstdc++: add experimental Contracts support
Date: Sat, 19 Nov 2022 12:50:15 +0000 [thread overview]
Message-ID: <CACb0b4mhGjG9b9WZWnCx-uY-0=r58zyg_pT_v7TW3qVbcLvnTA@mail.gmail.com> (raw)
In-Reply-To: <adcd6584-9fee-0bf0-4754-3b7034bed38b@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 367 bytes --]
On Sat, 19 Nov 2022 at 02:40, Jason Merrill <jason@redhat.com> wrote:
>
> Thanks, this is what I'm pushing:
>
Great.
I wonder if we should move the contents of libstdc++fs.a and
libstdc++_libbacktrace.a into libstdc++exp.a and make the former libraries
into linker scripts that point to libstdc++exp.a
It would be easier to only have one lib for unstable things.
prev parent reply other threads:[~2022-11-19 12:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-03 19:57 Jason Merrill
2022-11-18 18:17 ` Jonathan Wakely
2022-11-19 2:40 ` Jason Merrill
2022-11-19 12:50 ` Jonathan Wakely [this message]
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='CACb0b4mhGjG9b9WZWnCx-uY-0=r58zyg_pT_v7TW3qVbcLvnTA@mail.gmail.com' \
--to=jwakely@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jason@redhat.com \
--cc=libstdc++@gcc.gnu.org \
/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).