public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "edlinger at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/23623] volatile keyword changes bitfield access size from 32bit to 8bit Date: Wed, 11 Dec 2013 16:59:00 -0000 [thread overview] Message-ID: <bug-23623-4-nrLWZ6PGHg@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-23623-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=23623 --- Comment #19 from edlinger at gcc dot gnu.org --- Author: edlinger Date: Wed Dec 11 16:59:24 2013 New Revision: 205897 URL: http://gcc.gnu.org/viewcvs?rev=205897&root=gcc&view=rev Log: 2013-12-11 Bernd Edlinger <bernd.edlinger@hotmail.de> Sandra Loosemore <sandra@codesourcery.com> PR middle-end/23623 PR middle-end/48784 PR middle-end/56341 PR middle-end/56997 * expmed.c (strict_volatile_bitfield_p): Add bitregion_start and bitregion_end parameters. Test for compliance with C++ memory model. (store_bit_field): Adjust call to strict_volatile_bitfield_p. Add fallback logic for cases where -fstrict-volatile-bitfields is supposed to apply, but cannot. (extract_bit_field): Likewise. Use narrow_bit_field_mem and extract_fixed_bit_field_1 to do the extraction. (extract_fixed_bit_field): Revert to previous mode selection algorithm. Call extract_fixed_bit_field_1 to do the real work. (extract_fixed_bit_field_1): New function. testsuite: * gcc.dg/pr23623.c: Update to test interaction with C++ memory model. Modified: trunk/gcc/ChangeLog trunk/gcc/expmed.c trunk/gcc/testsuite/ChangeLog trunk/gcc/testsuite/gcc.dg/pr23623.c
next prev parent reply other threads:[~2013-12-11 16:59 UTC|newest] Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-23623-4@http.gcc.gnu.org/bugzilla/> 2013-06-08 19:57 ` sandra at codesourcery dot com 2013-06-14 2:59 ` sandra at codesourcery dot com 2013-10-07 15:40 ` sandra at codesourcery dot com 2013-12-11 16:50 ` edlinger at gcc dot gnu.org 2013-12-11 16:59 ` edlinger at gcc dot gnu.org [this message] 2014-02-27 7:28 ` jye2 at gcc dot gnu.org [not found] <bug-23623-11259@http.gcc.gnu.org/bugzilla/> 2006-03-28 18:03 ` pbrook at gcc dot gnu dot org 2006-03-29 15:22 ` pbrook at gcc dot gnu dot org 2006-03-29 17:44 ` pbrook at gcc dot gnu dot org 2006-05-16 17:15 ` pinskia at gcc dot gnu dot org 2006-08-02 11:30 ` jason dot morgan at vpnsolutions dot uk dot com 2009-01-13 10:12 ` frikkie at zitera dot co dot za 2009-01-13 10:42 ` frikkie at zitera dot co dot za 2009-01-13 15:52 ` frikkie at zitera dot co dot za 2005-08-29 14:11 [Bug c/23623] New: " m dot reszat at kostal dot com 2005-08-29 15:39 ` [Bug middle-end/23623] " pinskia at gcc dot gnu dot org 2005-08-29 16:21 ` pinskia at gcc dot gnu dot org 2005-08-29 21:27 ` falk at debian dot org 2005-08-30 7:59 ` m dot reszat at kostal dot com 2005-08-30 12:44 ` falk at debian dot org 2005-08-30 12:51 ` rearnsha at gcc dot gnu dot org 2005-08-30 13:42 ` m dot reszat at kostal dot com 2005-08-30 14:06 ` rearnsha at gcc dot gnu dot org 2005-09-08 15:12 ` m dot reszat at kostal 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-23623-4-nrLWZ6PGHg@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).