public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "joseph at codesourcery dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/48685] [4.5/4.6/4.7 regression] ICE in gimplify_expr, at gimplify.c:7034 Date: Thu, 21 Apr 2011 15:37:00 -0000 [thread overview] Message-ID: <bug-48685-4-8D1KXCHR5u@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-48685-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48685 --- Comment #4 from joseph at codesourcery dot com <joseph at codesourcery dot com> 2011-04-21 15:36:26 UTC --- The C front end should not depend on fold creating NON_LVALUE_EXPRs anywhere, but I don't know if C++ has such dependencies. Where does the NON_LVALUE_EXPR come from? In any case, I don't think NON_LVALUE_EXPR should be used for type conversions; a NON_LVALUE_EXPR with void type should only ever be used if the contained expression has void type (with the same qualifiers), and under those conditions STRIP_TYPE_NOPS should remove it. c_fully_fold_internal needs to preserve the type of the expression, so can't just remove a NON_LVALUE_EXPR that changes the type without adding some other conversion to the new type - but as noted above, if a NON_LVALUE_EXPR is changing the type I think the creation of that NON_LVALUE_EXPR is what's wrong.
next prev parent reply other threads:[~2011-04-21 15:37 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-04-19 14:50 [Bug middle-end/48685] New: " doko at ubuntu dot com 2011-04-19 15:05 ` [Bug middle-end/48685] " rguenth at gcc dot gnu.org 2011-04-19 15:08 ` [Bug c/48685] " rguenth at gcc dot gnu.org 2011-04-20 8:09 ` jakub at gcc dot gnu.org 2011-04-21 9:26 ` rguenth at gcc dot gnu.org 2011-04-21 15:37 ` joseph at codesourcery dot com [this message] 2011-04-22 11:43 ` jakub at gcc dot gnu.org 2011-04-22 16:54 ` joseph at codesourcery dot com 2011-04-22 19:20 ` jakub at gcc dot gnu.org 2011-04-23 10:19 ` jakub at gcc dot gnu.org 2011-04-23 10:19 ` jakub at gcc dot gnu.org 2011-04-23 10:21 ` [Bug c/48685] [4.5 Regression] " jakub at gcc dot gnu.org 2011-04-28 15:53 ` rguenth at gcc dot gnu.org 2011-05-03 17:11 ` jakub at gcc dot gnu.org 2011-05-03 17:19 ` 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-48685-4-8D1KXCHR5u@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).