public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "burnus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/60762] [ASAN] -fsanitize=address fails with LTO
Date: Sat, 05 Apr 2014 08:20:00 -0000	[thread overview]
Message-ID: <bug-60762-4-gQuAucAah7@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-60762-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60762

--- Comment #1 from Tobias Burnus <burnus at gcc dot gnu.org> ---
Hmm, the problem turns out to be more subtle: I compiled the same program on
CentOS 6.4 and on openSUSE 13.1. Result:

* On CentOS, both binaries fail with the assert (also independent of the use
  of a linker plugin)
* On openSUSE, both binaries work fine.

Also copying libasan.so to the other system made no difference. While without
-flto, the code runs fine on CentOS 6.4.


  reply	other threads:[~2014-04-05  8:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-04 16:02 [Bug middle-end/60762] New: " burnus at gcc dot gnu.org
2014-04-05  8:20 ` burnus at gcc dot gnu.org [this message]
2021-12-23  7:12 ` [Bug middle-end/60762] " 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-60762-4-gQuAucAah7@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).