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 tree-optimization/104970] [12 Regression] ICE in execute_todo, at passes.cc:2133 since r12-6480-gea19c8f33a3a8d2b
Date: Thu, 24 Mar 2022 09:40:54 +0000	[thread overview]
Message-ID: <bug-104970-4-NkgTzwe4N3@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-104970-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #11 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Siddhesh Poyarekar
<siddhesh@gcc.gnu.org>:

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

commit r12-7794-gc1d233e3334df07cfb4f732ace4d93d3cbc28bca
Author: Siddhesh Poyarekar <siddhesh@gotplt.org>
Date:   Wed Mar 23 23:09:02 2022 +0530

    tree-optimization/104970: Limit size computation for access attribute

    Limit object size computation only to the simple case where access
    attribute has been explicitly specified.  The object passed to
    __builtin_dynamic_object_size could either be a pointer or a VLA whose
    size has been described using access attribute.

    Further, return a valid size only if the object is a void * pointer or
    points to (or is a VLA of) a type that has a constant size.

    gcc/ChangeLog:

            PR tree-optimization/104970
            * tree-object-size.cc (parm_object_size): Restrict size
            computation scenarios to explicit access attributes.

    gcc/testsuite/ChangeLog:

            PR tree-optimization/104970
            * gcc.dg/builtin-dynamic-object-size-0.c (test_parmsz_simple2,
            test_parmsz_simple3, test_parmsz_extern, test_parmsz_internal,
            test_parmsz_internal2, test_parmsz_internal3): New tests.
            (main): Use them.

    Signed-off-by: Siddhesh Poyarekar <siddhesh@gotplt.org>

  parent reply	other threads:[~2022-03-24  9:40 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-17 15:24 [Bug tree-optimization/104970] New: " marxin at gcc dot gnu.org
2022-03-17 15:24 ` [Bug tree-optimization/104970] " marxin at gcc dot gnu.org
2022-03-17 17:50 ` siddhesh at gcc dot gnu.org
2022-03-21 11:59 ` [Bug tree-optimization/104970] [12 Regression] " jakub at gcc dot gnu.org
2022-03-21 12:19 ` jakub at gcc dot gnu.org
2022-03-21 17:19 ` msebor at gcc dot gnu.org
2022-03-21 17:22 ` msebor at gcc dot gnu.org
2022-03-21 18:18 ` jakub at gcc dot gnu.org
2022-03-22  0:25 ` msebor at gcc dot gnu.org
2022-03-23  5:56 ` siddhesh at gcc dot gnu.org
2022-03-23  7:28 ` jakub at gcc dot gnu.org
2022-03-23 15:34 ` msebor at gcc dot gnu.org
2022-03-24  9:40 ` cvs-commit at gcc dot gnu.org [this message]
2022-03-24  9:42 ` siddhesh at gcc dot gnu.org
2023-03-28 21:53 ` muecker at gwdg dot de
2023-03-29 11:15 ` siddhesh at gcc dot gnu.org
2023-03-30 17:17 ` muecker at gwdg dot de

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-104970-4-NkgTzwe4N3@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).