public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "siddhesh 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: Wed, 23 Mar 2022 05:56:47 +0000 [thread overview]
Message-ID: <bug-104970-4-5XVvmJfMjt@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 #8 from Siddhesh Poyarekar <siddhesh at gcc dot gnu.org> ---
(In reply to Martin Sebor from comment #7)
> The dollar sign in the internal attr_access string implies a VLA bound and
> the attr_access::vla_bounds() function queries the VLA bounds. That should
> make it possible to distinguish the two cases.
I noticed a attr_access.internal_p which has the following comment in
attribs.c:
/* Forms containing the square bracket are internal-only
(not specified by an attribute declaration), and used
for various forms of array and VLA parameters. */
That should be a good differentiator right? It fixes the motivating case here.
This is what I'm testing a bit more extensively.
diff --git a/gcc/tree-object-size.cc b/gcc/tree-object-size.cc
index b0b50774936..1e87739eda6 100644
--- a/gcc/tree-object-size.cc
+++ b/gcc/tree-object-size.cc
@@ -1477,7 +1477,7 @@ parm_object_size (struct object_size_info *osi, tree var)
tree typesize = TYPE_SIZE_UNIT (TREE_TYPE (TREE_TYPE (parm)));
tree sz = NULL_TREE;
- if (access && access->sizarg != UINT_MAX)
+ if (access && access->sizarg != UINT_MAX && !access->internal_p)
{
tree fnargs = DECL_ARGUMENTS (fndecl);
tree arg = NULL_TREE;
next prev parent reply other threads:[~2022-03-23 5:56 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 [this message]
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
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-5XVvmJfMjt@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).