public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "glisse at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug other/59622] [4.9 Regression] internal compiler error: verify_gimple failed
Date: Sun, 29 Dec 2013 17:17:00 -0000 [thread overview]
Message-ID: <bug-59622-4-JnoyG9eFW8@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-59622-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59622
Marc Glisse <glisse at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2013-12-29
Target Milestone|--- |4.9.0
Summary|trunk gcc-4.9.0:internal |[4.9 Regression] internal
|compiler error: |compiler error:
|verify_gimple failed |verify_gimple failed
Ever confirmed|0 |1
--- Comment #2 from Marc Glisse <glisse at gcc dot gnu.org> ---
Seems related to OBJ_TYPE_REF. -O2 is sufficient.
next prev parent reply other threads:[~2013-12-29 17:17 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-29 16:46 [Bug other/59622] New: trung gcc-4.9.0:internal " nheghathivhistha at gmail dot com
2013-12-29 17:17 ` glisse at gcc dot gnu.org [this message]
2013-12-29 18:12 ` [Bug other/59622] [4.9 Regression] internal " trippels at gcc dot gnu.org
2013-12-30 7:39 ` trippels at gcc dot gnu.org
2013-12-30 10:16 ` jakub at gcc dot gnu.org
2013-12-30 10:49 ` [Bug tree-optimization/59622] " jakub at gcc dot gnu.org
2013-12-30 10:53 ` jakub at gcc dot gnu.org
2013-12-30 21:29 ` hubicka at gcc dot gnu.org
2013-12-30 21:33 ` hubicka at gcc dot gnu.org
2013-12-31 4:54 ` nheghathivhistha at gmail dot com
2013-12-31 7:47 ` nheghathivhistha at gmail dot com
2013-12-31 11:57 ` jakub at gcc dot gnu.org
2013-12-31 12:12 ` jakub at gcc dot gnu.org
2014-01-02 13:06 ` jakub at gcc dot gnu.org
2014-01-02 17:01 ` hubicka at ucw dot cz
2014-01-09 20:33 ` jakub at gcc dot gnu.org
2014-01-09 21:01 ` jakub 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-59622-4-JnoyG9eFW8@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).