public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Qing Zhao <qing.zhao@oracle.com>
To: richard.guenther@gmail.com, dmalcolm@redhat.com
Cc: sam@gentoo.org, keescook@chromium.org, pinskia@gmail.com,
	gcc-patches@gcc.gnu.org, Qing Zhao <qing.zhao@oracle.com>
Subject: [PATCH v4 0/3][RFC]Provide more contexts for -Warray-bounds and -Wstringop-* warning messages
Date: Tue,  5 Nov 2024 16:31:29 +0000	[thread overview]
Message-ID: <20241105163132.1922052-1-qing.zhao@oracle.com> (raw)

Hi,

This is the 4th version of the patch for fixing PR109071.

Compared to the 3nd version:
https://gcc.gnu.org/pipermail/gcc-patches/2024-October/666870.html
https://gcc.gnu.org/pipermail/gcc-patches/2024-October/666872.html
https://gcc.gnu.org/pipermail/gcc-patches/2024-October/666871.html

The major improvements to this patch are:

1. Divide the patch into 3 parts:
    Part 1: Add new data structure move_history, record move_history during
            transformation;
    Part 2: In warning analysis, Use the new move_history to form a rich
            location with a sequence of events, to report more context info
            of the warnings.
    Part 3: Add debugging mechanism for move_history.

2. Major change to the above Part 2, completely rewritten based on David's
   new class lazy_diagnostic_path. 

3. Fix all issues identied By Sam;
   A. fix PR117375 (Bug in tree-ssa-sink.cc);
   B. documentation clarification;
   C. Add all the duplicated PRs in the commit comments;

4. Bootstrap GCC with the new -fdiagnostics-details on by default (Init (1)).
   exposed some ICE similar as PR117375 in tree-ssa-sink.cc, fixed.


bootstrapping and regression testing on both x86 and aarch64.

Please let me know any comment and suggestion.

Thanks.

Qing
Qing Zhao (3):
  Provide more contexts for -Warray-bounds, -Wstringop-* warning
    messages due to code movements from compiler transformation (Part 1)
    [PR109071,PR85788,PR88771,PR106762,PR108770,PR115274,PR117179]
  Provide more contexts for -Warray-bounds, -Wstringop-* warning
    messages due to code movements from compiler transformation (Part 2)
    [PR109071,PR85788,PR88771,PR106762,PR108770,PR115274,PR117179]
  Provide more contexts for -Warray-bounds, -Wstringop-* warning
    messages due to code movements from compiler transformation (Part 3)
    [PR109071,PR85788,PR88771,PR106762,PR108770,PR115274,PR117179]



             reply	other threads:[~2024-11-05 16:31 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-05 16:31 Qing Zhao [this message]
2024-11-05 16:31 ` [PATCH v4 1/3][RFC] Provide more contexts for -Warray-bounds, -Wstringop-* warning messages due to code movements from compiler transformation (Part 1) [PR109071,PR85788,PR88771,PR106762,PR108770,PR115274,PR117179] Qing Zhao
2024-11-05 16:31 ` [PATCH v4 2/3][RFC] Provide more contexts for -Warray-bounds, -Wstringop-* warning messages due to code movements from compiler transformation (Part 2) [PR109071,PR85788,PR88771,PR106762,PR108770,PR115274,PR117179] Qing Zhao
2024-11-05 19:29   ` David Malcolm
2024-11-05 19:36     ` Qing Zhao
2024-11-05 16:31 ` [PATCH v4 3/3][RFC] Provide more contexts for -Warray-bounds, -Wstringop-* warning messages due to code movements from compiler transformation (Part 3) [PR109071,PR85788,PR88771,PR106762,PR108770,PR115274,PR117179] Qing Zhao
2024-11-15 15:34 ` Ping: [PATCH v4 0/3][RFC]Provide more contexts for -Warray-bounds and -Wstringop-* warning messages Qing Zhao
2024-11-26 15:30   ` 2nd " Qing Zhao
2024-12-05 15:15     ` 3rd Ping: [Middle-end][PATCH " Qing Zhao
2024-12-06 18:32       ` Sam James
2024-12-23 17:29         ` 4th " Qing Zhao
2025-01-13 16:16           ` 5th " Qing Zhao
2025-02-05 18:28             ` Kees Cook
2024-11-17  5:13 ` [PATCH " Kees Cook
2024-11-18 14:57   ` Qing Zhao

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=20241105163132.1922052-1-qing.zhao@oracle.com \
    --to=qing.zhao@oracle.com \
    --cc=dmalcolm@redhat.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=keescook@chromium.org \
    --cc=pinskia@gmail.com \
    --cc=richard.guenther@gmail.com \
    --cc=sam@gentoo.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).