public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "kevin at koconnor dot net" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/66110] uint8_t memory access not optimized Date: Mon, 11 May 2015 18:10:00 -0000 [thread overview] Message-ID: <bug-66110-4-YZjxzZTRGG@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-66110-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66110 Kevin OConnor <kevin at koconnor dot net> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|INVALID |FIXED --- Comment #2 from Kevin OConnor <kevin at koconnor dot net> --- I understand that it is not incorrect to produce two redundant stores with the sample code. However, I do believe it would be correct to produce a single store. As such, I think this is an opportunity to improve gcc's optimization. That is, I think gcc could validly interpret the C spec so that two redundant uint8_t stores could be replaced with one. If this is not the best place to discuss that, what would be the best forum?
next prev parent reply other threads:[~2015-05-11 18:10 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-05-11 17:02 [Bug tree-optimization/66110] New: " kevin at koconnor dot net 2015-05-11 17:59 ` [Bug tree-optimization/66110] " pinskia at gcc dot gnu.org 2015-05-11 18:10 ` kevin at koconnor dot net [this message] 2015-05-12 9:17 ` [Bug middle-end/66110] " rguenth at gcc dot gnu.org 2015-05-12 13:19 ` rguenth at gcc dot gnu.org 2015-05-13 10:54 ` rguenth at gcc dot gnu.org 2015-05-13 10:54 ` rguenth at gcc dot gnu.org 2015-05-13 15:43 ` kevin at koconnor dot net 2015-05-18 15:41 ` kevin at koconnor dot net 2015-05-18 15:52 ` schwab@linux-m68k.org 2015-05-18 16:05 ` kevin at koconnor dot net 2015-05-18 20:43 ` joseph at codesourcery dot com 2015-05-18 22:28 ` kevin at koconnor dot net 2015-05-19 8:50 ` rguenther at suse dot de
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-66110-4-YZjxzZTRGG@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).