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 target/52080] Stores to bitfields introduce a store-data-race on adjacent data
Date: Wed, 14 Mar 2012 11:01:00 -0000	[thread overview]
Message-ID: <bug-52080-4-yxZWFcapxK@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-52080-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52080

--- Comment #13 from Richard Guenther <rguenth at gcc dot gnu.org> 2012-03-14 10:55:16 UTC ---
Author: rguenth
Date: Wed Mar 14 10:55:09 2012
New Revision: 185379

URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=185379
Log:
2012-03-14  Richard Guenther  <rguenther@suse.de>

    * tree.h (DECL_BIT_FIELD_REPRESENTATIVE): New define.
    * stor-layout.c (start_bitfield_representative): New function.
    (finish_bitfield_representative): Likewise.
    (finish_bitfield_layout): Likewise.
    (finish_record_layout): Call finish_bitfield_layout.
    * tree.c (free_lang_data_in_decl): Only free DECL_QUALIFIER
    for QUAL_UNION_TYPE fields.
    * tree-streamer-in.c (lto_input_ts_field_decl_tree_pointers):
    Stream DECL_BIT_FIELD_REPRESENTATIVE.
    * tree-streamer-out.c (write_ts_field_decl_tree_pointers): Likewise.

    PR middle-end/52080
    PR middle-end/52097
    PR middle-end/48124
    * expr.c (get_bit_range): Unconditionally extract bitrange
    from DECL_BIT_FIELD_REPRESENTATIVE.
    (expand_assignment): Adjust call to get_bit_range.

    * gcc.dg/torture/pr48124-1.c: New testcase.
    * gcc.dg/torture/pr48124-2.c: Likewise.
    * gcc.dg/torture/pr48124-3.c: Likewise.
    * gcc.dg/torture/pr48124-4.c: Likewise.

Added:
    trunk/gcc/testsuite/gcc.dg/torture/pr48124-1.c
    trunk/gcc/testsuite/gcc.dg/torture/pr48124-2.c
    trunk/gcc/testsuite/gcc.dg/torture/pr48124-3.c
    trunk/gcc/testsuite/gcc.dg/torture/pr48124-4.c
Modified:
    trunk/gcc/ChangeLog
    trunk/gcc/expr.c
    trunk/gcc/stor-layout.c
    trunk/gcc/testsuite/ChangeLog
    trunk/gcc/tree-streamer-in.c
    trunk/gcc/tree-streamer-out.c
    trunk/gcc/tree.c
    trunk/gcc/tree.h


  parent reply	other threads:[~2012-03-14 11:00 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-01 10:07 [Bug target/52080] New: " rguenth at gcc dot gnu.org
2012-02-01 10:23 ` [Bug target/52080] " rguenth at gcc dot gnu.org
2012-02-01 10:25 ` rguenth at gcc dot gnu.org
2012-02-01 10:39 ` rguenth at gcc dot gnu.org
2012-02-01 11:13 ` rguenth at gcc dot gnu.org
2012-02-01 17:12 ` ebotcazou at gcc dot gnu.org
2012-02-01 17:45 ` ebotcazou at gcc dot gnu.org
2012-02-01 17:50 ` matz at gcc dot gnu.org
2012-02-01 18:53 ` bergner at gcc dot gnu.org
2012-02-02 11:01 ` gcc-bugs at tesarici dot cz
2012-02-02 11:11 ` rguenth at gcc dot gnu.org
2012-02-02 12:40 ` gcc-bugs at tesarici dot cz
2012-02-21 12:04 ` rguenth at gcc dot gnu.org
2012-03-14 11:00 ` rguenth at gcc dot gnu.org
2012-03-14 11:01 ` rguenth at gcc dot gnu.org [this message]
2012-06-04  8:44 ` rguenth at gcc dot gnu.org
2013-02-19 20:37 ` LpSolit at netscape dot net
2014-02-16 13:17 ` jackie.rosen at hushmail 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-52080-4-yxZWFcapxK@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: link
Be 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).