public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug driver/63837] [5 Regression] r217391 causes kernel build errors with GCC_COMPARE_DEBUG=1
Date: Thu, 13 Nov 2014 09:21:00 -0000 [thread overview]
Message-ID: <bug-63837-4-p7hshmtmAh@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-63837-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63837
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |WAITING
Target Milestone|--- |5.0
--- Comment #4 from Richard Biener <rguenth at gcc dot gnu.org> ---
>From reading here it sounds like this is a kernel makefile bug, not a GCC one?
next prev parent reply other threads:[~2014-11-13 9:21 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-12 18:07 [Bug driver/63837] New: " trippels at gcc dot gnu.org
2014-11-12 23:56 ` [Bug driver/63837] " manu at gcc dot gnu.org
2014-11-13 2:41 ` trippels at gcc dot gnu.org
2014-11-13 2:47 ` pinskia at gcc dot gnu.org
2014-11-13 9:21 ` rguenth at gcc dot gnu.org [this message]
2014-11-13 9:57 ` trippels at gcc dot gnu.org
2014-11-13 13:36 ` manu at gcc dot gnu.org
2014-11-13 13:49 ` trippels at gcc dot gnu.org
2014-11-15 7:11 ` pinskia at gcc dot gnu.org
2014-11-15 11:16 ` manu at gcc dot gnu.org
2014-11-16 22:03 ` trippels at gcc dot gnu.org
2014-11-17 21:24 ` jakub at gcc dot gnu.org
2014-11-19 15:34 ` manu at gcc dot gnu.org
2014-11-19 15:40 ` trippels at gcc dot gnu.org
2014-11-19 16:38 ` jakub at gcc dot gnu.org
2014-11-19 18:12 ` jakub at gcc dot gnu.org
2014-11-19 18:38 ` trippels 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-63837-4-p7hshmtmAh@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).