From: Jonathan Wakely <jwakely@redhat.com>
To: Jakub Jelinek <jakub@redhat.com>
Cc: libstdc++@gcc.gnu.org, gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] libstdc++: Regenerate baseline_symbols.txt files for i386-linux-gnu
Date: Thu, 11 Apr 2024 15:07:52 +0100 [thread overview]
Message-ID: <CACb0b4mgxDZ-ATR6MvdSHLR0iVJjJuzB3dLVpzX56RGn_84U=A@mail.gmail.com> (raw)
In-Reply-To: <ZhfuaimOYd/0PABA@tucnak>
On Thu, 11 Apr 2024 at 15:07, Jakub Jelinek wrote:
>
> On Thu, Apr 11, 2024 at 02:59:05PM +0100, Jonathan Wakely wrote:
> > I think we also want the same change for i386.
> >
> > -- >8 --
> >
> > libstdc++-v3/ChangeLog:
> >
> > * config/abi/post/i386-linux-gnu/baseline_symbols.txt:
> > Regenerate.
>
> Not sure about that, the file is missing all the 3.4.30, 3.4.31 and other
> 3.4.32 symbols as well.
> It needs to be regenerated.
Oh right, yeah there's more missing.
> I'm not really sure what i386 really is and if we support it at all, given
> that it doesn't support the fundamental locking instructions.
True.
next prev parent reply other threads:[~2024-04-11 14:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-11 13:51 [PATCH] libstdc++: Regenerate baseline_symbols.txt files for Linux Jakub Jelinek
2024-04-11 13:53 ` Jonathan Wakely
2024-04-11 13:59 ` [PATCH] libstdc++: Regenerate baseline_symbols.txt files for i386-linux-gnu Jonathan Wakely
2024-04-11 14:06 ` Jakub Jelinek
2024-04-11 14:07 ` Jonathan Wakely [this message]
2024-04-11 14:11 ` [PATCH] libstdc++: Regenerate baseline_symbols.txt files for Linux Andreas Schwab
2024-04-11 14:13 ` Jonathan Wakely
2024-04-11 14:16 ` Jonathan Wakely
2024-04-11 14:18 ` Jakub Jelinek
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='CACb0b4mgxDZ-ATR6MvdSHLR0iVJjJuzB3dLVpzX56RGn_84U=A@mail.gmail.com' \
--to=jwakely@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jakub@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).