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 middle-end/109609] [12/13 Regression] tail call for function even when passing a ptr which references a local array still
Date: Wed, 26 Apr 2023 09:34:02 +0000	[thread overview]
Message-ID: <bug-109609-4-eouIvejuVh@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-109609-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #18 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-13 branch has been updated by Richard Biener
<rguenth@gcc.gnu.org>:

https://gcc.gnu.org/g:df49e4602882eabe0642699fb71a70f6e120e263

commit r13-7252-gdf49e4602882eabe0642699fb71a70f6e120e263
Author: Richard Biener <rguenther@suse.de>
Date:   Tue Apr 25 14:56:44 2023 +0200

    tree-optimization/109609 - correctly interpret arg size in fnspec

    By majority vote and a hint from the API name which is
    arg_max_access_size_given_by_arg_p this interprets a memory access
    size specified as given as other argument such as for strncpy
    in the testcase which has "1cO313" as specifying the _maximum_
    size read/written rather than the exact size.  There are two
    uses interpreting it that way already and one differing.  The
    following adjusts the differing and clarifies the documentation.

            PR tree-optimization/109609
            * attr-fnspec.h (arg_max_access_size_given_by_arg_p):
            Clarify semantics.
            * tree-ssa-alias.cc (check_fnspec): Correctly interpret
            the size given by arg_max_access_size_given_by_arg_p as
            maximum, not exact, size.

            * gcc.dg/torture/pr109609.c: New testcase.

    (cherry picked from commit e8d00353017f895d03a9eabae3506fd126ce1a2d)

  parent reply	other threads:[~2023-04-26  9:34 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-24 19:34 [Bug c++/109609] New: Invalid strncpy/strncat optimization in GCC 12 gburca-gnu at ebixio dot com
2023-04-24 19:38 ` [Bug middle-end/109609] " pinskia at gcc dot gnu.org
2023-04-24 19:40 ` pinskia at gcc dot gnu.org
2023-04-24 19:47 ` [Bug middle-end/109609] [12/13/14 Regression] " jakub at gcc dot gnu.org
2023-04-24 19:50 ` pinskia at gcc dot gnu.org
2023-04-24 19:52 ` [Bug middle-end/109609] [12/13/14 Regression] tail call for function even when passing a ptr which references a local array still jakub at gcc dot gnu.org
2023-04-24 19:56 ` pinskia at gcc dot gnu.org
2023-04-24 20:30 ` gburca-gnu at ebixio dot com
2023-04-24 20:52 ` jakub at gcc dot gnu.org
2023-04-25  6:30 ` rguenth at gcc dot gnu.org
2023-04-25  7:06 ` rguenth at gcc dot gnu.org
2023-04-25  7:15 ` rguenth at gcc dot gnu.org
2023-04-25  7:37 ` jakub at gcc dot gnu.org
2023-04-25  7:42 ` jakub at gcc dot gnu.org
2023-04-25 12:54 ` rguenth at gcc dot gnu.org
2023-04-25 14:53 ` cvs-commit at gcc dot gnu.org
2023-04-25 14:53 ` [Bug middle-end/109609] [12/13 " rguenth at gcc dot gnu.org
2023-04-25 16:14 ` gburca-gnu at ebixio dot com
2023-04-26  9:34 ` cvs-commit at gcc dot gnu.org [this message]
2023-04-26 10:41 ` cvs-commit at gcc dot gnu.org
2023-04-26 10:43 ` rguenth 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-109609-4-eouIvejuVh@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).