public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug sanitizer/105531] [13 regression] Recent libsanitizer imports breaks Solaris 11.3 build
Date: Fri, 22 Jul 2022 11:18:46 +0000 [thread overview]
Message-ID: <bug-105531-4-Y7A7wN8ocM@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-105531-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105531
--- Comment #1 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Rainer Orth <ro@gcc.gnu.org>:
https://gcc.gnu.org/g:786e51648bd9a6880339329380751809fb97cd6d
commit r13-1797-g786e51648bd9a6880339329380751809fb97cd6d
Author: Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE>
Date: Fri Jul 22 13:18:14 2022 +0200
libsanitizer: Fix Solaris 11.3 compilation [PR105531]
The libsanitizer build has been broken on Solaris 11.3 by the latest
import. An upstream patch to fix this has now been committed:
[sanitizer_common] Support Solaris < 11.4 in GetStaticTlsBoundary
https://reviews.llvm.org/D120059
I'd like to cherry-pick it into libsanitizer, too.
Bootstrapped without regressions on sparc-sun-solaris2.11,
i386-pc-solaris2.11 (both Solaris 11.3 and 11.4), and
x86_64-pc-linux-gnu.
2022-07-21 Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE>
libsanitizer:
PR sanitizer/105531
* sanitizer_common/sanitizer_linux_libcdep.cpp,
sanitizer_common/sanitizer_solaris.h:: Cherry-pick
llvm-project revision 3776db9a4fd2080d23d6a5f52e405eea44558761.
next prev parent reply other threads:[~2022-07-22 11:18 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-09 10:23 [Bug sanitizer/105531] New: " ro at gcc dot gnu.org
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 [this message]
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-Y7A7wN8ocM@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).