public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Andreas Schwab <schwab@suse.de>
To: Andreas Schwab via Libc-alpha <libc-alpha@sourceware.org>
Cc: Joseph Myers <joseph@codesourcery.com>,  jakub@redhat.com
Subject: Re: Update _FloatN header support for C++ in GCC 13
Date: Thu, 29 Sep 2022 17:12:42 +0200	[thread overview]
Message-ID: <mvm5yh6i591.fsf@suse.de> (raw)
In-Reply-To: <mvmh70qieo9.fsf@suse.de> (Andreas Schwab via Libc-alpha's message of "Thu, 29 Sep 2022 13:49:10 +0200")

I have now worked around that by building gcc once against the last
glibc release.  I guess nothing can be done about that anyway.

-- 
Andreas Schwab, SUSE Labs, schwab@suse.de
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE  1748 E4D4 88E3 0EEA B9D7
"And now for something completely different."

      reply	other threads:[~2022-09-29 15:12 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-28  0:23 Joseph Myers
2022-09-28 18:28 ` Jakub Jelinek
2022-09-29 11:49 ` Andreas Schwab
2022-09-29 15:12   ` Andreas Schwab [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=mvm5yh6i591.fsf@suse.de \
    --to=schwab@suse.de \
    --cc=jakub@redhat.com \
    --cc=joseph@codesourcery.com \
    --cc=libc-alpha@sourceware.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).