public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug sanitizer/64435] [5 Regression] Bootstrap failure in libsanitizer on AArch64 with Linux kernel <= 3.15 Date: Sun, 18 Jan 2015 19:11:00 -0000 [thread overview] Message-ID: <bug-64435-4-Oht7XxT0QL@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-64435-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64435 Jakub Jelinek <jakub at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW Last reconfirmed| |2015-01-18 Ever confirmed|0 |1 --- Comment #9 from Jakub Jelinek <jakub at gcc dot gnu.org> --- I've used: --- libsanitizer/sanitizer_common/sanitizer_platform_limits_posix.h 2014-11-14 00:10:33.735060963 +0100 +++ libsanitizer/sanitizer_common/sanitizer_platform_limits_posix.h 2015-01-18 14:43:05.812763769 +0100 @@ -167,7 +167,7 @@ namespace __sanitizer { unsigned __seq; u64 __unused1; u64 __unused2; -#elif defined(__mips__) +#elif defined(__mips__) || defined(__aarch64__) unsigned int mode; unsigned short __seq; unsigned short __pad1; --- libsanitizer/sanitizer_common/sanitizer_platform_limits_posix.cc 2014-11-14 00:10:33.735060963 +0100 +++ libsanitizer/sanitizer_common/sanitizer_platform_limits_posix.cc 2015-01-18 14:47:18.901482608 +0100 @@ -1055,7 +1055,10 @@ CHECK_SIZE_AND_OFFSET(ipc_perm, uid); CHECK_SIZE_AND_OFFSET(ipc_perm, gid); CHECK_SIZE_AND_OFFSET(ipc_perm, cuid); CHECK_SIZE_AND_OFFSET(ipc_perm, cgid); +#if !defined(__aarch64__) || !SANITIZER_LINUX || __GNUC_PREREQ (2, 21) +/* On aarch64 glibc 2.20 and earlier provided incorrect mode field. */ CHECK_SIZE_AND_OFFSET(ipc_perm, mode); +#endif CHECK_TYPE_SIZE(shmid_ds); CHECK_SIZE_AND_OFFSET(shmid_ds, shm_perm); to fix the #c6 issue. That said, seems asan is totally broken at least in Fedora 22/aarch64, but at least it builds with this and r223925 cherry-pick. Pretty much every test dies with AddressSanitizer CHECK failed: ../../../../libsanitizer/asan/asan_poisoning.cc:24 "((AddrIsInMem(addr))) != (0)
next prev parent reply other threads:[~2015-01-18 19:11 UTC|newest] Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-12-29 15:41 [Bug sanitizer/64435] New: [5.0.0 " david.abdurachmanov at gmail dot com 2014-12-29 18:21 ` [Bug sanitizer/64435] " david.abdurachmanov at gmail dot com 2014-12-29 18:25 ` david.abdurachmanov at gmail dot com 2015-01-09 11:20 ` rguenth at gcc dot gnu.org 2015-01-09 11:54 ` david.abdurachmanov at gmail dot com 2015-01-13 11:24 ` [Bug sanitizer/64435] [5 " rguenth at gcc dot gnu.org 2015-01-13 15:45 ` jakub at gcc dot gnu.org 2015-01-13 21:17 ` clyon at gcc dot gnu.org 2015-01-18 12:38 ` jakub at gcc dot gnu.org 2015-01-18 19:07 ` david.abdurachmanov at gmail dot com 2015-01-18 19:11 ` jakub at gcc dot gnu.org [this message] 2015-01-18 19:37 ` pinskia at gcc dot gnu.org 2015-01-18 19:51 ` clyon at gcc dot gnu.org 2015-01-19 8:40 ` jakub at gcc dot gnu.org 2015-01-19 16:53 ` jakub at gcc dot gnu.org 2015-01-19 17:29 ` jakub at gcc dot gnu.org 2015-01-19 17:55 ` pinskia at gcc dot gnu.org 2015-01-19 17:56 ` jakub at gcc dot gnu.org 2015-01-19 18:01 ` jakub at gcc dot gnu.org 2015-01-19 18:33 ` jakub at gcc dot gnu.org 2015-01-19 20:13 ` clyon at gcc dot gnu.org 2015-01-19 21:49 ` jakub at gcc dot gnu.org 2015-01-20 8:10 ` jakub at gcc dot gnu.org 2015-01-20 16:53 ` kcc at gcc dot gnu.org 2015-01-21 21:22 ` jakub at gcc dot gnu.org 2015-01-21 22:09 ` jakub at gcc dot gnu.org 2015-01-26 15:18 ` jakub 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-64435-4-Oht7XxT0QL@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: linkBe 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).