public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "hp at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug rtl-optimization/15296] [3.4 only] Delayed branch scheduling causing invalid code on cris-* Date: Thu, 27 May 2004 11:18:00 -0000 [thread overview] Message-ID: <20040526180422.3374.qmail@sourceware.org> (raw) In-Reply-To: <20040505140818.15296.hp@gcc.gnu.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
next prev parent reply other threads:[~2004-05-26 18:04 UTC|newest] Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top 2004-05-05 14:08 [Bug optimization/15296] New: " hp at gcc dot gnu dot org 2004-05-05 14:09 ` [Bug optimization/15296] " hp at gcc dot gnu dot org 2004-05-05 16:05 ` hp at gcc dot gnu dot org 2004-05-07 3:20 ` cvs-commit at gcc dot gnu dot org 2004-05-07 3:22 ` cvs-commit at gcc dot gnu dot org 2004-05-07 3:24 ` hp at gcc dot gnu dot org 2004-05-07 3:30 ` [Bug optimization/15296] [3.3/3.4 only] " pinskia at gcc dot gnu dot org 2004-05-17 11:22 ` [Bug rtl-optimization/15296] " gdr at gcc dot gnu dot org 2004-05-26 19:46 ` cvs-commit at gcc dot gnu dot org 2004-05-26 19:54 ` cvs-commit at gcc dot gnu dot org 2004-05-27 9:42 ` [Bug rtl-optimization/15296] [3.4 " hp at bitrange dot com 2004-05-27 9:56 ` hp at gcc dot gnu dot org 2004-05-27 10:28 ` pinskia at gcc dot gnu dot org 2004-05-27 11:18 ` hp at gcc dot gnu dot org [this message] 2004-05-27 11:22 ` bangerth at dealii dot org 2004-05-27 11:37 ` hp at bitrange dot com 2004-05-27 11:37 ` hp at bitrange dot com 2004-05-27 11:47 ` bangerth at dealii dot org 2004-05-27 14:02 ` hp at bitrange dot com 2004-05-27 14:40 ` bangerth at dealii dot org 2004-05-27 15:23 ` hp at gcc dot gnu dot org 2004-06-06 3:56 ` giovannibajo at libero dot it 2004-06-07 14:24 ` mmitchel at gcc dot gnu dot org 2004-06-12 22:16 ` mmitchel at gcc dot gnu dot org 2004-06-13 1:59 ` cvs-commit at gcc dot gnu dot org 2004-06-13 2:00 ` giovannibajo at libero dot it
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=20040526180422.3374.qmail@sourceware.org \ --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).