[Bug rtl-optimization/15296] [3.4 only] Delayed branch scheduling causing invalid code on cris-*

["hp at gcc dot gnu dot org" <gcc-bugzilla at gcc dot gnu dot org>]

------- Additional Comments From hp at gcc dot gnu dot org  2004-05-26 18:04 -------
I really think so.  How can you *know* that the test-case
succeeds in 3.5.0 when until it's released?  These "known to"
fields are an indication from a user, not a statement from a
developer: that's what "target milestone" is for.  With your
interpretation one of "known to" and "target milestone" fields
would be redundant, and there would not be a field to specify
what *released* versions are known to work/fail.  The "reported 
against" is just the first spotting.  Now please *do not* change
it again without proper references.

If you think my interpretation is incorrect, do take it up on
gcc@ (please CC: me, I'm behind on the list reading) and/or  
point me to the proper documentation.  I can't find anything
specific for the "known to" fields at
<URL:http://gcc.gnu.org/management.html> or
<URL:http://www.bugzilla.org/docs/html/> (but target
milestone is documented).


-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
      Known to work|3.3.4 3.5.0                 |


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