public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/13756] [tree-ssa] documentation missing
Date: Mon, 31 May 2021 00:35:34 +0000	[thread overview]
Message-ID: <bug-13756-4-WDoGatn741@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-13756-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #18 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
Note libmudflap was removed back in 2014.

libgfortran is still there though.
Someone has to audit the comments here to figure out if there is anything else
to be done.

       reply	other threads:[~2021-05-31  0:35 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-13756-4@http.gcc.gnu.org/bugzilla/>
2021-05-31  0:35 ` pinskia at gcc dot gnu.org [this message]
2024-03-26  4:21 ` egallager at gcc dot gnu.org
     [not found] <bug-13756-91@http.gcc.gnu.org/bugzilla/>
2005-12-27  0:38 ` pinskia at gcc dot gnu dot org
2007-09-05 19:48 ` rask at gcc dot gnu dot org
2004-01-20  3:26 [Bug other/13756] New: tree-ssa documentation missing in the internals manual dnovillo at gcc dot gnu dot org
2004-05-14 13:26 ` [Bug tree-optimization/13756] [tree-ssa] documentation missing jsm28 at gcc dot gnu dot org
2004-05-21 21:38 ` pinskia at gcc dot gnu dot org
2004-05-31 11:49 ` jsm28 at gcc dot gnu dot org
2004-08-13 10:08 ` jsm28 at gcc dot gnu dot org
2005-01-05  2:10 ` pinskia at gcc dot gnu dot org
2005-04-21  5:01 ` mmitchel at gcc dot gnu dot org
2005-07-08  1:38 ` mmitchel at gcc dot gnu dot org
2005-09-27 18:21 ` 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-13756-4-WDoGatn741@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).