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 middle-end/50199] [4.7 Regression] wrong code with -flto -fno-merge-constants Date: Thu, 08 Dec 2011 15:05:00 -0000 [thread overview] Message-ID: <bug-50199-4-s6fbYcvwFE@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-50199-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50199 --- Comment #5 from Richard Guenther <rguenth at gcc dot gnu.org> 2011-12-08 15:02:34 UTC --- Created attachment 26022 --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=26022 gimple predicate patches GIMPLE predicate patches - that will now commit STRING_CSTs to a local temporary via the static enum gimplify_status gimplify_addr_expr (tree *expr_p, gimple_seq *pre_p, gimple_seq *post_p) { ... default: /* We use fb_either here because the C frontend sometimes takes the address of a call that returns a struct; see gcc.dg/c99-array-lval-1.c. The gimplifier will correctly make the implied temporary explicit. */ /* Make the operand addressable. */ ret = gimplify_expr (&TREE_OPERAND (expr, 0), pre_p, post_p, is_gimple_addressable, fb_either); which is of course bogus.
next prev parent reply other threads:[~2011-12-08 15:03 UTC|newest] Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-08-26 19:45 [Bug middle-end/50199] New: " zsojka at seznam dot cz 2011-08-27 8:39 ` [Bug middle-end/50199] " rguenth at gcc dot gnu.org 2011-08-27 10:16 ` Joseph S. Myers 2011-08-27 11:29 ` joseph at codesourcery dot com 2011-10-27 10:13 ` rguenth at gcc dot gnu.org 2011-12-08 14:39 ` rguenth at gcc dot gnu.org 2011-12-08 15:05 ` rguenth at gcc dot gnu.org [this message] 2012-01-03 18:07 ` hubicka at gcc dot gnu.org 2012-01-04 9:32 ` rguenther at suse dot de 2012-01-04 12:58 ` hubicka at gcc dot gnu.org 2012-01-04 13:05 ` rguenther at suse dot de 2012-01-04 13:14 ` hubicka at ucw dot cz 2012-01-09 14:28 ` rguenth at gcc dot gnu.org 2012-01-09 15:20 ` hubicka at ucw dot cz 2013-01-11 16:03 ` [Bug middle-end/50199] [4.7/4.8 " jakub at gcc dot gnu.org 2013-01-14 14:46 ` rguenther at suse dot de 2013-01-14 14:56 ` jakub at gcc dot gnu.org 2013-03-22 14:42 ` [Bug middle-end/50199] [4.7/4.8/4.9 " jakub at gcc dot gnu.org 2013-05-31 10:57 ` jakub at gcc dot gnu.org 2013-10-16 9:50 ` jakub at gcc dot gnu.org 2014-05-22 9:01 ` [Bug middle-end/50199] [4.7/4.8/4.9/4.10 " rguenth at gcc dot gnu.org 2014-12-19 13:39 ` [Bug middle-end/50199] [4.8/4.9/5 " jakub at gcc dot gnu.org 2015-06-23 8:22 ` [Bug middle-end/50199] [4.8/4.9/5/6 " rguenth at gcc dot gnu.org 2015-06-26 20:11 ` [Bug middle-end/50199] [4.9/5/6 " jakub at gcc dot gnu.org 2015-06-26 20:37 ` 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-50199-4-s6fbYcvwFE@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).