public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ro at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/110077] [14 regression] libstdc++-abi/abi_check FAILs on Solaris
Date: Thu, 29 Jun 2023 12:55:23 +0000	[thread overview]
Message-ID: <bug-110077-4-wH1DrJPJps@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-110077-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #8 from Rainer Orth <ro at gcc dot gnu.org> ---
(In reply to Jonathan Wakely from comment #6)
> This is going to be hard for me to figure out without access to a Solaris
> x86 system.

There's hope that at least one, maybe two, Solaris 11.4/x86 systems can be
added to the cfarm.  As always, the primary problem is politics...

> Could you please attach the output of this command using GCC trunk on
> solaris x86?
> 
> g++ -std=c++23 -include charconv -x c++ /dev/null -E -dD

Sure, done.

  parent reply	other threads:[~2023-06-29 12:55 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-01 10:57 [Bug libstdc++/110077] New: " ro at gcc dot gnu.org
2023-06-01 10:57 ` [Bug libstdc++/110077] " ro at gcc dot gnu.org
2023-06-01 10:58 ` redi at gcc dot gnu.org
2023-06-01 11:00 ` redi at gcc dot gnu.org
2023-06-09 10:17 ` redi at gcc dot gnu.org
2023-06-09 12:26 ` cvs-commit at gcc dot gnu.org
2023-06-09 12:26 ` redi at gcc dot gnu.org
2023-06-12 11:26 ` ro at gcc dot gnu.org
2023-06-29 12:46 ` redi at gcc dot gnu.org
2023-06-29 12:54 ` ro at gcc dot gnu.org
2023-06-29 12:55 ` ro at gcc dot gnu.org [this message]
2023-06-29 13:33 ` redi at gcc dot gnu.org
2023-06-29 14:41 ` redi at gcc dot gnu.org
2023-06-29 14:42 ` redi at gcc dot gnu.org
2023-06-29 14:52 ` redi at gcc dot gnu.org
2023-06-30 13:54 ` ro at CeBiTec dot Uni-Bielefeld.DE
2023-06-30 14:47 ` redi at gcc dot gnu.org
2023-07-19 20:14 ` redi at gcc dot gnu.org
2023-07-19 22:43 ` cvs-commit at gcc dot gnu.org
2023-07-19 22:45 ` redi at gcc dot gnu.org
2023-07-21 11:35 ` ro at CeBiTec dot Uni-Bielefeld.DE
2023-07-21 13:04 ` redi 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-110077-4-wH1DrJPJps@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).