public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: David Malcolm <dmalcolm@redhat.com>
To: Martin Jambor <mjambor@suse.cz>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [committed] Document new analyzer parameters
Date: Thu, 20 Jul 2023 10:59:31 -0400	[thread overview]
Message-ID: <f639eb73a8832fd03ac8661b62156ba43df82461.camel@redhat.com> (raw)
In-Reply-To: <ri6ilaemyh0.fsf@suse.cz>

On Thu, 2023-07-20 at 16:47 +0200, Martin Jambor wrote:
> Hi,
> 
> This patch documents the analyzer parameters introduced in
> r14-2029-g0e466e978c7286 also in gcc/doc/invoke.texi.
> 
> Committed as obvious after testing with make pdf and make info and
> eyeballing the result.
> 
> Thanks,

Thanks
Dave


      reply	other threads:[~2023-07-20 14:59 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-31 18:06 [PATCH 0/3] Add diagram support to gcc diagnostics David Malcolm
2023-05-31 18:06 ` [PATCH 1/3] testsuite: move handle-multiline-outputs to before check for blank lines David Malcolm
2023-06-12 23:11   ` PING: " David Malcolm
2023-06-20 17:21     ` PING^2: " David Malcolm
2023-06-21 16:24       ` Mike Stump
2023-05-31 18:06 ` [PATCH 2/3] diagnostics: add support for "text art" diagrams David Malcolm
2023-06-23 11:52   ` Alex Coplan
2023-06-23 14:36     ` [PATCH] text-art: remove explicit #include of C++ standard library headers David Malcolm
2023-06-23 15:35       ` Alex Coplan
2023-06-24  1:26         ` [pushed: v2] " David Malcolm
2023-05-31 18:06 ` [PATCH 3/3] analyzer: add text-art visualizations of out-of-bounds accesses [PR106626] David Malcolm
2023-06-30 14:40   ` Martin Jambor
2023-07-20 14:47     ` [committed] Document new analyzer parameters Martin Jambor
2023-07-20 14:59       ` David Malcolm [this message]

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=f639eb73a8832fd03ac8661b62156ba43df82461.camel@redhat.com \
    --to=dmalcolm@redhat.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=mjambor@suse.cz \
    /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).