public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "trippels at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/63356] Compilation failure where clang does not have problems
Date: Thu, 25 Sep 2014 14:30:00 -0000 [thread overview]
Message-ID: <bug-63356-4-ZLSKrNFtuS@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-63356-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63356
Markus Trippelsdorf <trippels at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Summary|[4.8/4.9/5 Regression] |Compilation failure where
|Compilation failure where |clang does not have
|clang does not have |problems
|problems |
--- Comment #11 from Markus Trippelsdorf <trippels at gcc dot gnu.org> ---
(In reply to Richard Biener from comment #10)
> What version of GCC works? That is, how is this a regression?
You're right it isn't.
next prev parent reply other threads:[~2014-09-25 14:30 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-24 9:06 [Bug c++/63356] New: " fiesh at zefix dot tv
2014-09-24 9:18 ` [Bug c++/63356] " trippels at gcc dot gnu.org
2014-09-24 9:34 ` redi at gcc dot gnu.org
2014-09-24 9:41 ` fiesh at zefix dot tv
2014-09-24 9:48 ` trippels at gcc dot gnu.org
2014-09-24 14:04 ` trippels at gcc dot gnu.org
2014-09-24 14:25 ` trippels at gcc dot gnu.org
2014-09-24 14:44 ` trippels at gcc dot gnu.org
2014-09-24 15:31 ` fiesh at zefix dot tv
2014-09-24 15:36 ` [Bug c++/63356] [4.8/4.9/5 Regression] " trippels at gcc dot gnu.org
2014-09-25 14:18 ` rguenth at gcc dot gnu.org
2014-09-25 14:30 ` trippels at gcc dot gnu.org [this message]
2014-12-19 13:34 ` [Bug c++/63356] " jakub at gcc dot gnu.org
2015-01-11 11:28 ` fiesh at zefix dot tv
2015-01-30 16:44 ` fiesh at zefix dot tv
2015-03-17 9:04 ` fiesh at zefix dot tv
2015-03-19 15:14 ` jason at gcc dot gnu.org
2015-06-23 8:58 ` rguenth at gcc dot gnu.org
2015-09-23 17:52 ` manu 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-63356-4-ZLSKrNFtuS@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).