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 sanitizer/105531] New: [13 regression] Recent libsanitizer imports breaks Solaris 11.3 build
Date: Mon, 09 May 2022 10:23:00 +0000 [thread overview]
Message-ID: <bug-105531-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105531
Bug ID: 105531
Summary: [13 regression] Recent libsanitizer imports breaks
Solaris 11.3 build
Product: gcc
Version: 13.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: sanitizer
Assignee: unassigned at gcc dot gnu.org
Reporter: ro at gcc dot gnu.org
CC: dodji at gcc dot gnu.org, dvyukov at gcc dot gnu.org,
jakub at gcc dot gnu.org, kcc at gcc dot gnu.org, marxin at gcc dot gnu.org
Target Milestone: ---
Target: i386-pc-solaris2.11, sparc-sun-solaris2.11
The recent libsanitizer import broke the build on Solaris 11.3, both SPARC and
x86:
/vol/gcc/src/hg/master/local/libsanitizer/sanitizer_common/sanitizer_linux_libcdep.cpp:
In function 'int __sanitizer::CollectStaticTlsBlocks(dl_phdr_info*,
std::size_t, void*)':
/vol/gcc/src/hg/master/local/libsanitizer/sanitizer_common/sanitizer_linux_libcdep.cpp:380:28:
error: 'struct dl_phdr_info' has no member named 'dlpi_tls_data'
380 | uptr begin = (uptr)info->dlpi_tls_data;
| ^~~~~~~~~~~~~
This happens because Solaris doesn't support dlpi_tls_data (and dlpi_tls_modid)
before Solaris 11.4 SRU 10.3.
It's not an issue for LLVM upstream which only support Solaris 11.4, but GCC
continues to support Solaris 11.3 as well.
I have an (abandoned) patch to fix this: https://reviews.llvm.org/D120059.
I'll
see if I can get it approved upstream (it needs slight modifications for
changes
to compiler-rt since it was submitted); otherwise it will have to be kept
gcc-local.
next reply other threads:[~2022-05-09 10:23 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-09 10:23 ro at gcc dot gnu.org [this message]
2022-05-09 10:23 ` [Bug sanitizer/105531] " ro at gcc dot gnu.org
2022-07-22 11:18 ` cvs-commit at gcc dot gnu.org
2022-07-22 11:20 ` ro at gcc dot gnu.org
2022-10-03 8:29 ` ebotcazou at gcc dot gnu.org
2022-10-03 9:45 ` marxin at gcc dot gnu.org
2022-10-03 9:49 ` ro at CeBiTec dot Uni-Bielefeld.DE
2022-10-03 9:50 ` marxin at gcc dot gnu.org
2022-10-03 9:54 ` ebotcazou at gcc dot gnu.org
2022-10-03 12:53 ` ro at gcc dot gnu.org
2022-10-03 14:10 ` marxin at gcc dot gnu.org
2022-10-03 14:11 ` marxin at gcc dot gnu.org
2022-10-03 14:29 ` cvs-commit at gcc dot gnu.org
2022-10-03 14:31 ` ro at CeBiTec dot Uni-Bielefeld.DE
2022-10-03 14:31 ` ro 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-105531-4@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).