public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "steven at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/26242] [4.1/4.2 Regression] VRP is not documented in passes.texi
Date: Sun, 28 May 2006 09:50:00 -0000	[thread overview]
Message-ID: <20060528095023.28290.qmail@sourceware.org> (raw)
In-Reply-To: <bug-26242-6528@http.gcc.gnu.org/bugzilla/>



------- Comment #4 from steven at gcc dot gnu dot org  2006-05-28 09:50 -------
It is sad that this is not release critical, and even worse that the
contributor of vrp apparently can't miss half an hour to document his work as
he is required to do.


-- 

steven at gcc dot gnu dot org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |NEW
     Ever Confirmed|0                           |1
   Last reconfirmed|0000-00-00 00:00:00         |2006-05-28 09:50:22
               date|                            |


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


  parent reply	other threads:[~2006-05-28  9:50 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-12 19:40 [Bug tree-optimization/26242] New: " pinskia at gcc dot gnu dot org
2006-02-12 19:41 ` [Bug tree-optimization/26242] " pinskia at gcc dot gnu dot org
2006-02-14  9:05 ` mmitchel at gcc dot gnu dot org
2006-02-28 20:42 ` mmitchel at gcc dot gnu dot org
2006-05-25  2:47 ` mmitchel at gcc dot gnu dot org
2006-05-28  9:50 ` steven at gcc dot gnu dot org [this message]
2006-05-29 14:58 ` dnovillo at gcc dot gnu dot org
2006-05-29 14:58 ` dnovillo at gcc dot gnu dot org
2006-05-29 15:28 ` dnovillo at gcc dot gnu dot org

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=20060528095023.28290.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: link
Be 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).