This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: FAIL: gcc.c-torture/execute/950628-1.c execution, -O1
- To: rth at redhat dot com
- Subject: Re: FAIL: gcc.c-torture/execute/950628-1.c execution, -O1
- From: kenner at vlsi1 dot ultra dot nyu dot edu (Richard Kenner)
- Date: Wed, 24 Jan 01 18:35:30 EST
- Cc: gcc-patches at gcc dot gnu dot org
This is almost certainly related to the /u sharing bits that
Richard Kenner and I have been discussing.
OK, I'm confused and I suspect lots of others are too.
Precisely which sets of /u operations are considered to conflict and
which are not?
Clearly a /u read and a /u write need to conflict for some purposes since
we can't schedule the read in front of the write. But which don't?