public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "colanderman at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug rtl-optimization/55360] [TileGX] Passing structure by value on stack needlessly writes to and reads from memory Date: Mon, 19 Nov 2012 18:48:00 -0000 [thread overview] Message-ID: <bug-55360-4-oq7zLKC2JY@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-55360-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55360 --- Comment #2 from Chris King <colanderman at gmail dot com> 2012-11-19 18:47:39 UTC --- Possibly, though I doubt it. PR 28831 has more to do with eliding copies of the struct in its entirety; the problem I'm having centers around accessing individual elements. If PR 28831 were the cause, I would expect both my test cases (with and without bit-fields) to behave identically, however they do not. It's possible that fixing PR 28831 may hide this bug in my particular use case (by avoiding the stack allocation in the first place), but I believe the difference in handling of normal fields vs. bit fields to be a distinct bug.
next prev parent reply other threads:[~2012-11-19 18:48 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-11-16 20:54 [Bug rtl-optimization/55360] New: " colanderman at gmail dot com 2012-11-16 23:46 ` [Bug rtl-optimization/55360] " hjl.tools at gmail dot com 2012-11-19 18:48 ` colanderman at gmail dot com [this message] 2022-11-09 15:59 ` 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-55360-4-oq7zLKC2JY@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).