public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "howarth at nitro dot med.uc.edu" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug sanitizer/55518] boehm-gc, libatomic, libffi and libgomp testsuite can't find path to libasan for make check with -fsanitizer
Date: Wed, 28 Nov 2012 18:24:00 -0000	[thread overview]
Message-ID: <bug-55518-4-2E48ujBaeq@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-55518-4@http.gcc.gnu.org/bugzilla/>


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

--- Comment #5 from Jack Howarth <howarth at nitro dot med.uc.edu> 2012-11-28 18:23:45 UTC ---
Considering that H.J. is working towards a --with-build-config=bootstrap-asan
option, it would seem wise to allow for testing the existing FSF gcc testsuite
against libasan without folks having to really hack up their source tree to do
so. Wasn't libsanitizer added to vet the code generation of FSF gcc? That would
place it in a slightly different category than say --fopenmp or -fgnu-tm.


  parent reply	other threads:[~2012-11-28 18:24 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-28 15:05 [Bug sanitizer/55518] New: " howarth at nitro dot med.uc.edu
2012-11-28 15:46 ` [Bug sanitizer/55518] " jakub at gcc dot gnu.org
2012-11-28 16:49 ` howarth at nitro dot med.uc.edu
2012-11-28 17:18 ` howarth at nitro dot med.uc.edu
2012-11-28 17:23 ` jakub at gcc dot gnu.org
2012-11-28 18:24 ` howarth at nitro dot med.uc.edu [this message]
2012-11-28 20:18 ` howarth at nitro dot med.uc.edu
2012-11-28 21:02 ` howarth at nitro dot med.uc.edu

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-55518-4-2E48ujBaeq@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).