public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jason at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/111067] g++.dg/opt/icf{1,2,3}.C tests fail on darwin
Date: Tue, 02 Apr 2024 22:04:01 +0000	[thread overview]
Message-ID: <bug-111067-4-yt7Ro3GoTk@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-111067-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #10 from Jason Merrill <jason at gcc dot gnu.org> ---
(In reply to Jonathan Wakely from comment #8)
> (In reply to Iain Sandoe from comment #7)
> > So I am actually asking if the extension actually has any useful meaning?
> 
> For non-darwin, yes, it requests the storage of two initializer lists to be
> merged (see the commit msg for r14-1500-g4d935f52b0d5c0).

Though that doesn't involve the attribute, and promoting init-lists to static
should work fine on darwin.

(In reply to Jonathan Wakely from comment #6)
> The question then is whether the attribute is supposed to be a non-binding
> request or not.
> 
> If it's a non-binding request then the test should be adjusted/unsupported
> for this target.

It is a non-binding request. And yes, if this optimization is problematic on
darwin, we should adjust the test.

  parent reply	other threads:[~2024-04-02 22:04 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-18 17:50 [Bug c++/111067] New: " fxcoudert at gcc dot gnu.org
2023-08-18 17:51 ` [Bug c++/111067] " fxcoudert at gcc dot gnu.org
2023-08-18 17:57 ` [Bug testsuite/111067] " pinskia at gcc dot gnu.org
2023-08-19 20:17 ` fxcoudert at gcc dot gnu.org
2023-08-21 12:44 ` iains at gcc dot gnu.org
2023-08-21 12:53 ` iains at gcc dot gnu.org
2024-03-07 23:37 ` [Bug c++/111067] " iains at gcc dot gnu.org
2024-04-02 20:01 ` redi at gcc dot gnu.org
2024-04-02 20:18 ` iains at gcc dot gnu.org
2024-04-02 20:41 ` redi at gcc dot gnu.org
2024-04-02 20:42 ` pinskia at gcc dot gnu.org
2024-04-02 22:04 ` jason at gcc dot gnu.org [this message]
2024-04-02 22:31 ` iains at gcc dot gnu.org
2024-04-02 22:47 ` jason at gcc dot gnu.org

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-111067-4-yt7Ro3GoTk@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).