public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Joseph Myers <joseph@codesourcery.com>
To: Jakub Jelinek <jakub@redhat.com>
Cc: Jonathan Wakely <jwakely@redhat.com>, <gcc-patches@gcc.gnu.org>,
	Bruce Korb <bkorb@gnu.org>
Subject: Re: [PATCH] c++: Implement P1467R9 - Extended floating-point types and standard names compiler part except for bfloat16 [PR106652]
Date: Tue, 13 Sep 2022 17:50:17 +0000	[thread overview]
Message-ID: <alpine.DEB.2.22.394.2209131748520.3083096@digraph.polyomino.org.uk> (raw)
In-Reply-To: <Yx+cEyCrrhs+tqf9@tucnak>

On Mon, 12 Sep 2022, Jakub Jelinek via Gcc-patches wrote:

> > We don't claim in glibc to support old snapshots from master, so checking 
> > for __GNUC_PREREQ (13, 0) and failing for such older GCC 13 versions is 
> > fine.
> 
> Ok, makes sense, especially if it is applied on the glibc side a few months
> after it is changed on the GCC side.  If it is applied immediately, there

Leaving the build of glibc C++ tests broken for months with mainline GCC 
doesn't seem like a good idea; it's a recipe for missing other 
regressions.  I think a fix should be applied to glibc immediately after 
the GCC change.

-- 
Joseph S. Myers
joseph@codesourcery.com

  parent reply	other threads:[~2022-09-13 17:50 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-12  8:05 Jakub Jelinek
2022-09-12 19:36 ` Joseph Myers
2022-09-12 20:52   ` Jakub Jelinek
2022-09-12 21:00     ` Jakub Jelinek
2022-09-13 17:50     ` Joseph Myers [this message]
2022-09-16 11:48 ` Jason Merrill
2022-09-16 17:34   ` Jakub Jelinek
2022-09-17  8:58     ` Jason Merrill
2022-09-19 16:39       ` Jakub Jelinek
2022-09-26 21:15         ` Jason Merrill
2022-09-26 22:11           ` Jakub Jelinek
2022-09-20  3:35 ` Hongtao Liu
2022-09-20  7:14   ` Hongtao Liu
2022-09-20  8:51   ` Jakub Jelinek
2022-09-22 15:56     ` [RFC PATCH] __trunc{tf,xf,df,sf,hf}bf2, __truncbfhf2 and __extendbfsf2 Jakub Jelinek
2022-09-23  0:44       ` Hongtao Liu

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=alpine.DEB.2.22.394.2209131748520.3083096@digraph.polyomino.org.uk \
    --to=joseph@codesourcery.com \
    --cc=bkorb@gnu.org \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=jakub@redhat.com \
    --cc=jwakely@redhat.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).