public inbox for libstdc++@gcc.gnu.org
 help / color / mirror / Atom feed
From: Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE>
To: Jakub Jelinek <jakub@redhat.com>
Cc: Jonathan Wakely <jwakely@redhat.com>,
	 Patrick Palka <ppalka@redhat.com>,
	 gcc-patches@gcc.gnu.org,  libstdc++@gcc.gnu.org
Subject: Re: [PATCH] libstdc++: Another attempt to ensure g++ 13+ compiled programs enforce gcc 13.2+ libstdc++.so.6 [PR108969]
Date: Tue, 02 May 2023 13:20:56 +0200	[thread overview]
Message-ID: <yddcz3jyo6f.fsf@CeBiTec.Uni-Bielefeld.DE> (raw)
In-Reply-To: <ZEt3EFFjFUijaFFx@tucnak> (Jakub Jelinek's message of "Fri, 28 Apr 2023 09:34:40 +0200")

Hi Jakub,

> Bootstrapped/regtested on x86_64-linux, i686-linux and sparc-sun-solaris2.11
>
> On the last one I've actually checked a version which had
> defined(_GLIBCXX_SYMVER_SUN) next to defined(_GLIBCXX_SYMVER_GNU), but
> init_priority attribute doesn't seem to be supported there and so I couldn't
> actually test how this works there.  Using gas and Sun ld, Rainer, does one
> need to use gas + gld for init_priority or something else?

it's complicated, as usual ;-)  While Solaris 11.3 ld has basic
.init_priority etc. support, it doesn't know about priorities, so the
support is disabled.  This is what you see on gcc211 in the cfarm.

Solaris 11.4 ld on the other hand added everything to make the configure
test work, so HAVE_INITFINI_ARRAY_SUPPORT is enabled.  Unfortunately,
there's still PR c++/52477 (dup of PR c++/81337) where g++ makes
unwarranted assumptions which happen to hold on Linux/glibc (only?), but
often break other targets (Solaris, Darwin, FreeBSD) in unexpected
places (like libsanitizer).  I've made at least two attempts at a fix
which got me nowhere, so I'm considering disabling
HAVE_INITFINI_ARRAY_SUPPORT on Solaris for good.  This is purely a g++
issue, clang++ gets this right.

	Rainer

-- 
-----------------------------------------------------------------------------
Rainer Orth, Center for Biotechnology, Bielefeld University

      parent reply	other threads:[~2023-05-02 11:20 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-28  7:34 Jakub Jelinek
2023-04-28  8:35 ` Jonathan Wakely
2023-04-28 22:02   ` Jakub Jelinek
2023-05-02 15:43     ` Jonathan Wakely
2023-05-02 11:20 ` Rainer Orth [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=yddcz3jyo6f.fsf@CeBiTec.Uni-Bielefeld.DE \
    --to=ro@cebitec.uni-bielefeld.de \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=jakub@redhat.com \
    --cc=jwakely@redhat.com \
    --cc=libstdc++@gcc.gnu.org \
    --cc=ppalka@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).