From ec56965643d368ba8eae4ce34af4439aa9dd7b31 Mon Sep 17 00:00:00 2001 From: Richard Kenner Date: Sun, 17 Sep 2000 15:33:30 +0000 Subject: [PATCH] alias.c (true_dependence): Allow non-unchanging read to conflict with unchanging write. * alias.c (true_dependence): Allow non-unchanging read to conflict with unchanging write. From-SVN: r36476 --- gcc/ChangeLog | 3 +++ gcc/alias.c | 5 ++++- 2 files changed, 7 insertions(+), 1 deletion(-) diff --git a/gcc/ChangeLog b/gcc/ChangeLog index 8c48b71bc32..cf7604279e7 100644 --- a/gcc/ChangeLog +++ b/gcc/ChangeLog @@ -13,6 +13,9 @@ Sun Sep 17 18:48:32 2000 Denis Chertykov Sun Sep 17 10:46:17 2000 Richard Kenner + * alias.c (true_dependence): Allow non-unchanging read to conflict + with unchanging write. + * expr.c (store_constructor_field): Accept ALIAS_SET arg. (store_constructor): Pass alias_set to it. diff --git a/gcc/alias.c b/gcc/alias.c index be46281dcfc..65b053f649b 100644 --- a/gcc/alias.c +++ b/gcc/alias.c @@ -1600,10 +1600,13 @@ true_dependence (mem, mem_mode, x, varies) A non-unchanging read can conflict with a non-unchanging write. An unchanging read can conflict with an unchanging write since there may be a single store to this address to initialize it. + Note that an unchanging store can conflict with a non-unchanging read + since we have to make conservative assumptions when we have a + record with readonly fields and we are copying the whole thing. Just fall through to the code below to resolve potential conflicts. This won't handle all cases optimally, but the possible performance loss should be negligible. */ - if (RTX_UNCHANGING_P (x) != RTX_UNCHANGING_P (mem)) + if (RTX_UNCHANGING_P (x) && ! RTX_UNCHANGING_P (mem)) return 0; if (mem_mode == VOIDmode) -- 2.30.2