public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "y.gribov at samsung dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug sanitizer/63646] libsanitizer fails to build for AARCH64:ILP32
Date: Mon, 27 Oct 2014 11:02:00 -0000 [thread overview]
Message-ID: <bug-63646-4-nPrgKAnfHp@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-63646-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63646
Yury Gribov <y.gribov at samsung dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |y.gribov at samsung dot com
--- Comment #4 from Yury Gribov <y.gribov at samsung dot com> ---
(In reply to Andrew Pinski from comment #2)
> Really I think sanitizer should be auto-generating this header rather than
> having its own copy.
People keep mentioning this but Asan team never seemed to bother. Actually
missing symbols is not the biggest problems because they at least manifest
themselves at build time. Have a look at bunch of lovely magic constants with
interspersing ifdefs all over the place in sanitizer_platform_limits_posix.h.
Debugging type mismatch issues at runtime is so fun.
prev parent reply other threads:[~2014-10-27 10:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-26 2:29 [Bug sanitizer/63646] New: " pinskia at gcc dot gnu.org
2014-10-26 5:59 ` [Bug sanitizer/63646] " pinskia at gcc dot gnu.org
2014-10-26 7:13 ` pinskia at gcc dot gnu.org
2014-10-27 11:02 ` y.gribov at samsung dot com [this message]
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-63646-4-nPrgKAnfHp@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).