public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "hjl.tools at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug sanitizer/59018] New: [4.9 Regression] libsanitizer doesn't build for x32 Date: Wed, 06 Nov 2013 10:26:00 -0000 [thread overview] Message-ID: <bug-59018-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59018 Bug ID: 59018 Summary: [4.9 Regression] libsanitizer doesn't build for x32 Product: gcc Version: 4.9.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: sanitizer Assignee: unassigned at gcc dot gnu.org Reporter: hjl.tools at gmail dot com 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 r204368 breaks x32. There are 4 problems: 1. internal_syscall casts pointers to uint64. It doesn't work for x32 since 32-bit pointers are signed extended to int64. They should be casted to uptr first. A patch is posted at http://gcc.gnu.org/ml/gcc-patches/2013-11/msg00403.html 2. internal_clone needs to allocate 2 int64 to restore 2 pointers by pop which only pops 64-bit integer into 64-bit register. Also "movq %6,%%r8\n" can't be used to load 32-bit pointer into 64-bit r8. We should let compiler handle it. A patch is posted at http://gcc.gnu.org/ml/gcc-patches/2013-11/msg00405.html 3. x32 uses the same file system calls as x86-64. The types used in those system calls must be the same for x32 and x86-64. A patch is posted at http://gcc.gnu.org/ml/gcc-patches/2013-11/msg00407.html 4. X32 uses the same FPU state as x86-64. We should check __x86_64 instead of __WORDSIZE == 64. A patch is posted at http://gcc.gnu.org/ml/gcc-patches/2013-11/msg00408.html All patches are tested on x32, x86-64 and x86.
next reply other threads:[~2013-11-06 10:26 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-11-06 10:26 hjl.tools at gmail dot com [this message] 2013-11-06 10:27 ` [Bug sanitizer/59018] " hjl.tools at gmail dot com 2013-11-06 17:48 ` jakub at gcc dot gnu.org 2013-11-06 17:58 ` kcc at gcc dot gnu.org 2013-11-06 18:01 ` kcc at gcc dot gnu.org 2013-11-06 18:04 ` hjl.tools at gmail dot com 2013-11-06 18:07 ` hjl.tools at gmail dot com 2013-11-06 18:15 ` kcc at gcc dot gnu.org 2013-11-06 21:51 ` hjl at gcc dot gnu.org 2013-11-06 21:52 ` hjl at gcc dot gnu.org 2013-11-06 21:53 ` hjl at gcc dot gnu.org 2013-11-06 21:54 ` hjl at gcc dot gnu.org 2013-11-06 23:54 ` hjl.tools at gmail dot com
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-59018-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: 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).