public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: gcc-patches@gcc.gnu.org
Subject: ASAN merge...
Date: Tue, 13 Nov 2012 05:07:00 -0000	[thread overview]
Message-ID: <20121113.000747.810968224853699322.davem@davemloft.net> (raw)


This has broken the build on every Linux target that hasn't added
the necessary cpu specific code to asan_linux.cc

I'm working on the sparc bits, but I'm really surprised this
happened.

             reply	other threads:[~2012-11-13  5:07 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-13  5:07 David Miller [this message]
2012-11-13 16:22 ` Diego Novillo
2012-11-13 16:52   ` H.J. Lu
2012-11-13 18:46   ` David Miller
2012-11-14 13:26     ` Dodji Seketeli
2012-11-14 17:06       ` David Miller
2012-11-13 21:19   ` Konstantin Serebryany
2012-11-13 22:31     ` Ramana Radhakrishnan
2012-11-13 22:41       ` Andrew Pinski
2012-11-13 23:19         ` Konstantin Serebryany
2012-11-14  1:03         ` Ramana Radhakrishnan
2012-11-14 13:49         ` Richard Earnshaw
2012-11-16  9:55           ` Andrew Haley
2012-11-16 15:35             ` Ian Lance Taylor
2012-11-16 15:43               ` Richard Earnshaw
2012-11-17 19:20               ` Toon Moene
2012-11-14 11:51   ` Dodji Seketeli

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=20121113.000747.810968224853699322.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=gcc-patches@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).