public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "sandra at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/951] Documentation of compiler passes and sources very out of date
Date: Sun, 23 Jun 2024 14:52:54 +0000	[thread overview]
Message-ID: <bug-951-4-IhfweobbW5@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-951-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=951

--- Comment #16 from sandra at gcc dot gnu.org ---
Given that this issue was filed >20 years ago and both the passlist and
documentation have changed drastically since then, I think the
originally-reported bugs are probably irrelevant and it's fine to close this
issue.  If there are still bugs in the internals passlist docs it would be more
helpful to have specific issues for each of them (e.g., missing/incorrect docs
for a particular pass or group of passes).  Or, just propose a patch to improve
the docs.  :-)

  parent reply	other threads:[~2024-06-23 14:52 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-951-4@http.gcc.gnu.org/bugzilla/>
2024-03-26  4:22 ` egallager at gcc dot gnu.org
2024-06-21  6:39 ` pinskia at gcc dot gnu.org
2024-06-21  7:36 ` rguenth at gcc dot gnu.org
2024-06-23  3:26 ` egallager at gcc dot gnu.org
2024-06-23 14:52 ` sandra at gcc dot gnu.org [this message]
2024-06-24  7:22 ` rguenth at gcc dot gnu.org
     [not found] <bug-951-230@http.gcc.gnu.org/bugzilla/>
2005-12-10  4:02 ` pinskia at gcc dot gnu dot org
     [not found] <20001201060600.951.jsm28@gcc.gnu.org>
2005-04-21  4:58 ` mmitchel at gcc dot gnu dot org
2005-07-01 22:11 ` pinskia 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=bug-951-4-IhfweobbW5@http.gcc.gnu.org/bugzilla/ \
    --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).