Message ID | 504A3AEB.6090605@redhat.com |
---|---|
State | New |
Headers | show |
On Fri, Sep 7, 2012 at 8:20 PM, Aldy Hernandez <aldyh@redhat.com> wrote: > This is a bit different, in that we don't currently have an infrastructure > to test transactional memory code within the simulate-thread framework. > Luckily for this test, the LIM pass has an actual dump message when it fails > to hoist a value due to its presence in a transaction. > > Eventually/ideally, we should have a mechanism for testing races of > transactionally executed code. > > OK? Ok. Thanks, Richard.
diff --git a/gcc/testsuite/gcc.dg/tm/reg-promotion.c b/gcc/testsuite/gcc.dg/tm/reg-promotion.c index 337c29f..e48bfb2 100644 --- a/gcc/testsuite/gcc.dg/tm/reg-promotion.c +++ b/gcc/testsuite/gcc.dg/tm/reg-promotion.c @@ -20,5 +20,5 @@ void func() } } -/* { dg-final { scan-tree-dump-times "MEM count_lsm.. count_lsm_flag" 1 "lim1" } } */ +/* { dg-final { scan-tree-dump-times "Cannot hoist conditional load of count because it is in a transaction" 1 "lim1" } } */ /* { dg-final { cleanup-tree-dump "lim1" } } */