public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "aldyh at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/51752] trans-mem: publication safety violated Date: Tue, 28 Feb 2012 20:10:00 -0000 [thread overview] Message-ID: <bug-51752-4-jvFn13fWdz@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-51752-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51752 --- Comment #7 from Aldy Hernandez <aldyh at gcc dot gnu.org> 2012-02-28 20:08:44 UTC --- Author: aldyh Date: Tue Feb 28 20:08:39 2012 New Revision: 184638 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=184638 Log: PR middle-end/51752 * gimple.h (gimple_in_transaction): New. (gimple_set_in_transaction): New. (struct gimple_statement_base): Add in_transaction field. * tree-ssa-loop-im.c: (movement_possibility): Restrict movement of transaction loads. (tree_ssa_lim_initialize): Compute transaction bits. * tree.h (compute_transaction_bits): Protoize. * trans-mem.c (tm_region_init): Use the heap to store BB auxilliary data. (compute_transaction_bits): New. Added: trunk/gcc/testsuite/gcc.dg/tm/pub-safety-1.c Modified: trunk/gcc/ChangeLog trunk/gcc/gimple.h trunk/gcc/trans-mem.c trunk/gcc/tree-ssa-loop-im.c
next prev parent reply other threads:[~2012-02-28 20:10 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-01-04 14:18 [Bug middle-end/51752] New: " torvald at gcc dot gnu.org 2012-01-04 19:18 ` [Bug middle-end/51752] " torvald at gcc dot gnu.org 2012-01-05 14:30 ` aldyh at gcc dot gnu.org 2012-01-06 14:03 ` torvald at gcc dot gnu.org 2012-02-09 16:24 ` aldyh at gcc dot gnu.org 2012-02-09 16:44 ` rguenth at gcc dot gnu.org 2012-02-09 17:40 ` rth at gcc dot gnu.org 2012-02-09 18:41 ` torvald at gcc dot gnu.org 2012-02-28 20:10 ` aldyh at gcc dot gnu.org [this message] 2012-03-16 19:15 ` aldyh 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-51752-4-jvFn13fWdz@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).