public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "hjl at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug sanitizer/59018] [4.9 Regression] libsanitizer doesn't build for x32 Date: Wed, 06 Nov 2013 21:51:00 -0000 [thread overview] Message-ID: <bug-59018-4-cyZ2JxLuqI@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-59018-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59018 --- Comment #9 from hjl at gcc dot gnu.org <hjl at gcc dot gnu.org> --- Author: hjl Date: Wed Nov 6 21:49:36 2013 New Revision: 204480 URL: http://gcc.gnu.org/viewcvs?rev=204480&root=gcc&view=rev Log: Cast pointers to uptr for 64-bit syscalls PR sanitizer/59018 * sanitizer_common/sanitizer_linux.cc (internal_mmap, internal_munmap, internal_open, internal_read, internal_write, internal_stat, internal_lstat, internal_fstat, internal_readlink, internal_unlink, internal_execve, NanoTime, BlockingMutex::Lock, BlockingMutex::Unlock, internal_ptrace, internal_getdents, internal_sigaltstack): Cast pointers to uptr for 64-bit syscalls. Modified: trunk/libsanitizer/ChangeLog trunk/libsanitizer/sanitizer_common/sanitizer_linux.cc
next prev parent reply other threads:[~2013-11-06 21:51 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-11-06 10:26 [Bug sanitizer/59018] New: " hjl.tools at gmail dot com 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 [this message] 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-cyZ2JxLuqI@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).