public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/109970] -Wstringop-overflow should work with parameter forward declarations
Date: Fri, 26 May 2023 21:31:45 +0000	[thread overview]
Message-ID: <bug-109970-4-GDIuG5zmmU@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-109970-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #1 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Martin Uecker <uecker@gcc.gnu.org>:

https://gcc.gnu.org/g:8d6bd830f5f9c939e8565c0341a0c6c588834484

commit r14-1304-g8d6bd830f5f9c939e8565c0341a0c6c588834484
Author: Martin Uecker <uecker@tugraz.at>
Date:   Fri May 26 11:19:01 2023 +0200

    c: -Wstringop-overflow for parameters with forward-declared sizes

    Warnings from -Wstringop-overflow do not appear for parameters declared
    as VLAs when the bound refers to a parameter forward declaration. This
    is fixed by splitting the loop that passes through parameters into two,
    first only recording the positions of all possible size expressions
    and then processing the parameters.

    PR c/109970

    gcc/c-family:

            * c-attribs.cc (build_attr_access_from_parms): Split loop to first
            record all parameters.

    gcc/testsuite:

            * gcc.dg/pr109970.c: New test.

  reply	other threads:[~2023-05-26 21:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-25 20:01 [Bug c/109970] New: " muecker at gwdg dot de
2023-05-26 21:31 ` cvs-commit at gcc dot gnu.org [this message]
2023-11-03 20:05 ` [Bug c/109970] " uecker at gcc dot gnu.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-109970-4-GDIuG5zmmU@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).