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 tree-optimization/51506] Function cloning misses constant struct Date: Mon, 12 Dec 2011 10:04:00 -0000 [thread overview] Message-ID: <bug-51506-4-xoWane9LwK@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-51506-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51506 Richard Guenther <rguenth at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW Last reconfirmed| |2011-12-12 CC| |jamborm at gcc dot gnu.org, | |rguenth at gcc dot gnu.org Ever Confirmed|0 |1 Severity|normal |enhancement --- Comment #1 from Richard Guenther <rguenth at gcc dot gnu.org> 2011-12-12 10:02:22 UTC --- We currently do not easily see that they are constant: D.1599.a = 6; D.1599.b = 1; D.1603_1 = compute_dint (D.1599, 1); but we could in theory improve our IL by not forcing the aggregate argument to a temporary during gimplification of rv = compute_dint (<<< Unknown tree: compound_literal_expr struct dint D.1599 = {.a=6, .b=1}; >>>, 1) + rv; but simply allow !is_gimple_reg_type CONSTRUCTORs that are TREE_CONSTANT, thus have D.1603_1 = compute_dint ({.a=6, .b=1}, 1); in the IL. That would still require ipa-cp to handle aggregates though. The above would also mean that D.1599 = {.a=6, .b=1}; would be valid GIMPLE (I see no good reason to disallow this either).
next prev parent reply other threads:[~2011-12-12 10:02 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-12-11 23:58 [Bug tree-optimization/51506] New: " peteraward+gcc at gmail dot com 2011-12-12 10:04 ` rguenth at gcc dot gnu.org [this message] 2011-12-13 2:21 ` [Bug tree-optimization/51506] " pinskia at gcc dot gnu.org 2021-07-19 3:06 ` [Bug ipa/51506] Function cloning misses constant struct at -Os vs -O2 pinskia 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-51506-4-xoWane9LwK@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).