public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "petro.karashchenko at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/94387] Excess read instructions are generated in case of writing to fields of volatile + packed type (structure) Date: Sun, 29 Mar 2020 14:28:33 +0000 [thread overview] Message-ID: <bug-94387-4-x5gSMuawQH@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-94387-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94387 --- Comment #1 from Petro Karashchenko <petro.karashchenko at gmail dot com> --- Also the ambiguity of the issue is that excess read instructions generation depends on type of the field. Excess reads are not generated when 8 bit types are accessed and generated when data types greater that 8 bits are accessed.
next prev parent reply other threads:[~2020-03-29 14:28 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-03-29 14:23 [Bug middle-end/94387] New: " petro.karashchenko at gmail dot com 2020-03-29 14:28 ` petro.karashchenko at gmail dot com [this message] 2020-03-29 22:41 ` [Bug middle-end/94387] " pinskia at gcc dot gnu.org 2020-03-29 22:43 ` pinskia at gcc dot gnu.org 2020-03-30 5:44 ` petro.karashchenko at gmail dot com 2020-03-30 8:17 ` rguenth at gcc dot gnu.org 2020-03-30 8:44 ` petro.karashchenko at gmail dot com 2020-04-19 20:16 ` petro.karashchenko at gmail dot com
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-94387-4-x5gSMuawQH@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).