public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "egallager at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/55656] objc/obj-c++ failures present under darwin11
Date: Tue, 08 Aug 2023 22:02:57 +0000	[thread overview]
Message-ID: <bug-55656-4-vUMFxDgnL1@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-55656-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=55656

--- Comment #10 from Eric Gallager <egallager at gcc dot gnu.org> ---
(In reply to Iain Sandoe from comment #9)
> (In reply to Eric Gallager from comment #8)
> > (In reply to Iain Sandoe from comment #7)
> > > fixed on master
> > > e.g.
> > > https://gcc.gnu.org/pipermail/gcc-testresults/2021-March/669584.html
> > 
> > So... are we keeping this open for backports, then? 
> 
> yes, most of the fixes are code-gen ones - so I think we need them on at
> least one branch that can be built with c++98.
> 
> > If so, to which branches?
> 
> 10.x .. not sure if it's necessary to go back further (let's see there might
> be a subset of the changes that are worth doing).

10.x is closed now...

      parent reply	other threads:[~2023-08-08 22:02 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-11 20:24 [Bug target/55656] New: " howarth at nitro dot med.uc.edu
2012-12-12 10:02 ` [Bug target/55656] [4.8 Regression] " rguenth at gcc dot gnu.org
2012-12-12 14:07 ` howarth at nitro dot med.uc.edu
2013-03-22 14:45 ` [Bug target/55656] " jakub at gcc dot gnu.org
2013-05-31 10:59 ` jakub at gcc dot gnu.org
2013-07-16 16:44 ` iains at gcc dot gnu.org
2013-10-16  9:49 ` jakub at gcc dot gnu.org
2015-06-22 14:25 ` rguenth at gcc dot gnu.org
2021-03-22  9:33 ` iains at gcc dot gnu.org
2021-03-22 22:28 ` egallager at gcc dot gnu.org
2021-03-22 23:11 ` iains at gcc dot gnu.org
2023-08-08 22:02 ` egallager at gcc dot gnu.org [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=bug-55656-4-vUMFxDgnL1@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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).