public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/65072] Segfault when parsing dectlype in trailing return type
Date: Fri, 20 Mar 2015 11:00:00 -0000 [thread overview]
Message-ID: <bug-65072-4-MshcXXld4m@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-65072-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65072
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jakub at gcc dot gnu.org
--- Comment #10 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
(In reply to Marek Polacek from comment #9)
> Likely started with r151360 -- which doesn't reveal much, this rev was a
> part of LTO merge, dealing with gimplification of types and symbols.
Actually, sorry for the error, it really started with r151529.
next prev parent reply other threads:[~2015-03-20 10:36 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-15 19:48 [Bug c++/65072] New: " uroc327 at cssbook dot de
2015-02-15 19:54 ` [Bug c++/65072] " uroc327 at cssbook dot de
2015-03-17 15:56 ` mpolacek at gcc dot gnu.org
2015-03-17 18:46 ` mpolacek at gcc dot gnu.org
2015-03-17 18:56 ` trippels at gcc dot gnu.org
2015-03-17 19:08 ` mpolacek at gcc dot gnu.org
2015-03-19 10:04 ` mpolacek at gcc dot gnu.org
2015-03-19 10:04 ` mpolacek at gcc dot gnu.org
2015-03-20 9:29 ` mpolacek at gcc dot gnu.org
2015-03-20 11:00 ` jakub at gcc dot gnu.org [this message]
2015-03-20 12:03 ` mpolacek at gcc dot gnu.org
2015-03-20 16:12 ` mpolacek at gcc dot gnu.org
2015-03-20 16:15 ` mpolacek 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-65072-4-MshcXXld4m@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).