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/100379] cyclades.h is removed from linux kernel header files
Date: Fri, 21 May 2021 11:17:45 +0000 [thread overview]
Message-ID: <bug-100379-4-15OBL9xvQw@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-100379-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100379
--- Comment #8 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-9 branch has been updated by Tamar Christina
<tnfchris@gcc.gnu.org>:
https://gcc.gnu.org/g:2b40941d23b1570cdd90083b58fa0f66aa58c86e
commit r9-9546-g2b40941d23b1570cdd90083b58fa0f66aa58c86e
Author: Tamar Christina <tamar.christina@arm.com>
Date: Fri May 21 12:16:56 2021 +0100
libsanitizer: Remove cyclades from libsanitizer
The Linux kernel has removed the interface to cyclades from
the latest kernel headers[1] due to them being orphaned for the
past 13 years.
libsanitizer uses this header when compiling against glibc, but
glibcs itself doesn't seem to have any references to cyclades.
Further more it seems that the driver is broken in the kernel and
the firmware doesn't seem to be available anymore.
As such since this is breaking the build of libsanitizer (and so the
GCC bootstrap[2]) I propose to remove this.
[1] https://lkml.org/lkml/2021/3/2/153
[2] https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100379
libsanitizer/ChangeLog:
PR sanitizer/100379
* sanitizer_common/sanitizer_common_interceptors_ioctl.inc:
Cherry-pick
llvm-project revision f7c5351552387bd43f6ca3631016d7f0dfe0f135.
* sanitizer_common/sanitizer_platform_limits_posix.cc: Likewise.
* sanitizer_common/sanitizer_platform_limits_posix.h: Likewise.
next prev parent reply other threads:[~2021-05-21 11:17 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-02 0:21 [Bug sanitizer/100379] New: " unlvsur at live dot com
2021-05-02 2:17 ` [Bug sanitizer/100379] " pinskia at gcc dot gnu.org
2021-05-05 12:46 ` vvinayag at arm dot com
2021-05-07 9:39 ` tnfchris at gcc dot gnu.org
2021-05-20 5:54 ` pinskia at gcc dot gnu.org
2021-05-21 9:31 ` cvs-commit at gcc dot gnu.org
2021-05-21 9:36 ` cvs-commit at gcc dot gnu.org
2021-05-21 9:40 ` cvs-commit at gcc dot gnu.org
2021-05-21 11:17 ` cvs-commit at gcc dot gnu.org [this message]
2021-05-21 11:19 ` tnfchris at gcc dot gnu.org
2021-09-17 6:36 ` pinskia 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-100379-4-15OBL9xvQw@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).