public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Martin Jambor <mjambor@suse.cz>
To: David Malcolm <dmalcolm@redhat.com>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH 3/3] analyzer: add text-art visualizations of out-of-bounds accesses [PR106626]
Date: Fri, 30 Jun 2023 16:40:29 +0200	[thread overview]
Message-ID: <ri64jmpnhcy.fsf@suse.cz> (raw)
In-Reply-To: <20230531180630.3127108-4-dmalcolm@redhat.com>

Hi David,

On Wed, May 31 2023, David Malcolm via Gcc-patches wrote:
> This patch extends -Wanalyzer-out-of-bounds so that, where possible, it
> will emit a text art diagram visualizing the spatial relationship between

[...]


>
> gcc/ChangeLog:
> 	PR analyzer/106626
> 	* Makefile.in (ANALYZER_OBJS): Add analyzer/access-diagram.o.
> 	* doc/invoke.texi (Wanalyzer-out-of-bounds): Add description of
> 	text art.
> 	(fanalyzer-debug-text-art): New.
>
> gcc/analyzer/ChangeLog:
> 	PR analyzer/106626
> 	* access-diagram.cc: New file.
> 	* access-diagram.h: New file.
> 	* analyzer.h (class region_offset): Add default ctor.
> 	(region_offset::make_byte_offset): New decl.
> 	(region_offset::concrete_p): New.
> 	(region_offset::get_concrete_byte_offset): New.
> 	(region_offset::calc_symbolic_bit_offset): New decl.
> 	(region_offset::calc_symbolic_byte_offset): New decl.
> 	(region_offset::dump_to_pp): New decl.
> 	(region_offset::dump): New decl.
> 	(operator<, operator<=, operator>, operator>=): New decls for
> 	region_offset.
> 	* analyzer.opt
> 	(-param=analyzer-text-art-string-ellipsis-threshold=): New.
> 	(-param=analyzer-text-art-string-ellipsis-head-len=): New.
> 	(-param=analyzer-text-art-string-ellipsis-tail-len=): New.
> 	(-param=analyzer-text-art-ideal-canvas-width=): New.

contrib/check-params-in-docs.py now complains that:

  $ ./gcc/xgcc -Bgcc --help=param &>/tmp/params.txt
  $ ../src/contrib/check-params-in-docs.py ../src/gcc/doc/invoke.texi /tmp/params.txt 
  Missing:
  @item analyzer-text-art-string-ellipsis-threshold
  The number of bytes at which to ellipsize string literals in

  @item analyzer-text-art-string-ellipsis-head-len
  The number of literal bytes to show at the head of a string

  @item analyzer-text-art-string-ellipsis-tail-len
  The number of literal bytes to show at the tail of a string

  @item analyzer-text-art-ideal-canvas-width
  The ideal width in characters of text art diagrams generated by the

Can you please add the respective documentation entries?

Thanks!

Martin

  reply	other threads:[~2023-06-30 14:40 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 [this message]
2023-07-20 14:47     ` [committed] Document new analyzer parameters Martin Jambor
2023-07-20 14:59       ` David Malcolm

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=ri64jmpnhcy.fsf@suse.cz \
    --to=mjambor@suse.cz \
    --cc=dmalcolm@redhat.com \
    --cc=gcc-patches@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).