public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "Joost.VandeVondele at mat dot ethz.ch" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug sanitizer/59188] [4.9 Regression] lib64/libtsan.so: undefined reference to `sigsetjmp'
Date: Thu, 21 Nov 2013 15:11:00 -0000	[thread overview]
Message-ID: <bug-59188-4-SyTFvJpCgs@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-59188-4@http.gcc.gnu.org/bugzilla/>

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

Joost VandeVondele <Joost.VandeVondele at mat dot ethz.ch> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |REOPENED
   Last reconfirmed|                            |2013-11-21
         Resolution|FIXED                       |---
     Ever confirmed|0                           |1

--- Comment #10 from Joost VandeVondele <Joost.VandeVondele at mat dot ethz.ch> ---
(In reply to Richard Biener from comment #9)
> Fixed
unlikely, the fix only went to the llvm repo so far.
>  (works for me now).
depends on your libc


  parent reply	other threads:[~2013-11-21 15:11 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-19 14:26 [Bug sanitizer/59188] New: " Joost.VandeVondele at mat dot ethz.ch
2013-11-19 14:52 ` [Bug sanitizer/59188] " rguenth at gcc dot gnu.org
2013-11-19 14:53 ` jakub at gcc dot gnu.org
2013-11-19 15:13 ` dvyukov at google dot com
2013-11-19 15:16 ` dvyukov at google dot com
2013-11-19 15:24 ` Joost.VandeVondele at mat dot ethz.ch
2013-11-19 15:34 ` dvyukov at google dot com
2013-11-21 11:55 ` dvyukov at google dot com
2013-11-21 15:02 ` redi at gcc dot gnu.org
2013-11-21 15:06 ` rguenth at gcc dot gnu.org
2013-11-21 15:11 ` Joost.VandeVondele at mat dot ethz.ch [this message]
2013-11-22 11:06 ` rguenth at gcc dot gnu.org
2013-11-22 11:11 ` kcc 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-59188-4-SyTFvJpCgs@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).