public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "glider at google dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/55289] darwin bootstrap fails due to missing libsanitizer/interception/mach_override directory and files
Date: Thu, 15 Nov 2012 08:18:00 -0000	[thread overview]
Message-ID: <bug-55289-4-yVJS9JyVmx@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-55289-4@http.gcc.gnu.org/bugzilla/>


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

--- Comment #39 from Alexander Potapenko <glider at google dot com> 2012-11-15 08:18:01 UTC ---
I agree with Kostya that no major changes to mach_override are necessary
because we are really going to dump it. However minor fixes required for ASan
in GCC to work on Darwin right now should be perfectly ok.

As there currently are issues blocking the dynamic ASan runtime (e.g.
https://code.google.com/p/address-sanitizer/issues/detail?id=124), and we still
depend on CoreFoundation I can't promise that we'll get rid of mach_override
before the GCC 4.8 release.


  parent reply	other threads:[~2012-11-15  8:18 UTC|newest]

Thread overview: 52+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-12 19:32 [Bug bootstrap/55289] New: " howarth at nitro dot med.uc.edu
2012-11-12 19:32 ` [Bug bootstrap/55289] " howarth at nitro dot med.uc.edu
2012-11-12 20:53 ` dominiq at lps dot ens.fr
2012-11-13  0:47 ` howarth at nitro dot med.uc.edu
2012-11-13 13:24 ` dominiq at lps dot ens.fr
2012-11-13 13:55 ` iains at gcc dot gnu.org
2012-11-13 14:07 ` howarth at nitro dot med.uc.edu
2012-11-13 14:11 ` dominiq at lps dot ens.fr
2012-11-13 14:30 ` howarth at nitro dot med.uc.edu
2012-11-13 14:39 ` howarth at nitro dot med.uc.edu
2012-11-13 19:50 ` howarth at nitro dot med.uc.edu
2012-11-13 19:52 ` howarth at nitro dot med.uc.edu
2012-11-13 20:13 ` howarth at nitro dot med.uc.edu
2012-11-13 20:21 ` howarth at nitro dot med.uc.edu
2012-11-13 20:26 ` howarth at nitro dot med.uc.edu
2012-11-13 20:50 ` howarth at nitro dot med.uc.edu
2012-11-13 21:27 ` konstantin.s.serebryany at gmail dot com
2012-11-13 21:55 ` howarth at nitro dot med.uc.edu
2012-11-13 22:14 ` howarth at nitro dot med.uc.edu
2012-11-13 23:21 ` dominiq at lps dot ens.fr
2012-11-14  1:29 ` howarth at nitro dot med.uc.edu
2012-11-14  1:30 ` howarth at nitro dot med.uc.edu
2012-11-14 14:24 ` howarth at nitro dot med.uc.edu
2012-11-14 14:46 ` howarth at nitro dot med.uc.edu
2012-11-14 15:52 ` howarth at nitro dot med.uc.edu
2012-11-14 16:00 ` howarth at nitro dot med.uc.edu
2012-11-14 16:02 ` howarth at nitro dot med.uc.edu
2012-11-14 16:03 ` howarth at nitro dot med.uc.edu
2012-11-14 16:06 ` howarth at nitro dot med.uc.edu
2012-11-14 16:14 ` glider at google dot com
2012-11-14 16:41 ` glider at google dot com
2012-11-14 16:54 ` howarth at nitro dot med.uc.edu
2012-11-14 19:10 ` howarth at nitro dot med.uc.edu
2012-11-14 20:21 ` konstantin.s.serebryany at gmail dot com
2012-11-14 20:57 ` howarth at nitro dot med.uc.edu
2012-11-14 22:09 ` howarth at nitro dot med.uc.edu
2012-11-14 23:10 ` konstantin.s.serebryany at gmail dot com
2012-11-14 23:49 ` dominiq at lps dot ens.fr
2012-11-15  2:07 ` howarth at nitro dot med.uc.edu
2012-11-15  2:10 ` howarth at nitro dot med.uc.edu
2012-11-15  8:18 ` glider at google dot com [this message]
2012-11-15 13:46 ` howarth at nitro dot med.uc.edu
2012-11-15 13:51 ` howarth at nitro dot med.uc.edu
2012-11-15 15:04 ` dominiq at lps dot ens.fr
2012-11-15 15:13 ` howarth at nitro dot med.uc.edu
2012-11-15 17:54 ` howarth at nitro dot med.uc.edu
2012-11-15 17:58 ` iains at gcc dot gnu.org
2012-11-15 18:29 ` howarth at nitro dot med.uc.edu
2012-11-15 19:09 ` howarth at nitro dot med.uc.edu
2012-11-15 19:19 ` howarth at nitro dot med.uc.edu
2012-11-22 10:43 ` [Bug sanitizer/55289] " glider at google dot com
2012-11-24 22:37 ` 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-55289-4-yVJS9JyVmx@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).