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 c++/61959] [4.8/4.9/4.10 Regression] ICE: in tree_to_uhwi, at tree.h:3657 when building Mozilla code Date: Wed, 30 Jul 2014 09:54:00 -0000 [thread overview] Message-ID: <bug-61959-4-csU2KuJHFw@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-61959-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61959 Richard Biener <rguenth at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Component|middle-end |c++ --- Comment #6 from Richard Biener <rguenth at gcc dot gnu.org> --- The constructor is invalid: (gdb) p debug_generic_expr (exp) {.D.2102={.x={.D.2071={.value=1}}, .y={.D.2071={.value=1}}}, .(struct A *) this + 8={}} the element index has to be a FIELD_DECL - 'this + 8' is not allowed here. C++ frontend issue.
next prev parent reply other threads:[~2014-07-30 9:54 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-07-29 21:43 [Bug c++/61959] New: "internal compiler error: Segmentation fault" " botond at mozilla dot com 2014-07-29 22:00 ` [Bug c++/61959] " pinskia at gcc dot gnu.org 2014-07-29 22:48 ` botond at mozilla dot com 2014-07-29 23:06 ` botond at mozilla dot com 2014-07-29 23:44 ` [Bug c++/61959] "internal compiler error: in tree_to_uhwi, at tree.h:3657" " botond at mozilla dot com 2014-07-30 4:31 ` [Bug middle-end/61959] [4.8/4.9/4.10 Regression] ICE: in tree_to_uhwi, at tree.h:3657 " trippels at gcc dot gnu.org 2014-07-30 9:54 ` rguenth at gcc dot gnu.org [this message] 2014-08-07 19:10 ` [Bug c++/61959] " jason at gcc dot gnu.org 2014-08-07 19:49 ` jason at gcc dot gnu.org 2014-08-07 19:49 ` jason at gcc dot gnu.org 2014-08-07 19:50 ` jason at gcc dot gnu.org 2014-08-07 19:51 ` jason 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-61959-4-csU2KuJHFw@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: linkBe 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).