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/109334] New: tree-object-size: Improve size computation in arguments Date: Wed, 29 Mar 2023 11:14:07 +0000 [thread overview] Message-ID: <bug-109334-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109334 Bug ID: 109334 Summary: tree-object-size: Improve size computation in arguments Product: gcc Version: 13.0 Status: UNCONFIRMED Keywords: ice-on-valid-code Severity: normal Priority: P3 Component: tree-optimization Assignee: unassigned at gcc dot gnu.org Reporter: siddhesh at gcc dot gnu.org CC: jakub at gcc dot gnu.org, marxin at gcc dot gnu.org, msebor at gcc dot gnu.org, muecker at gwdg dot de, siddhesh at gcc dot gnu.org Depends on: 104970 Target Milestone: --- The fix for bug 104970 is too restrictive, size computation should also work for VLA bounds and also cases where it could work without attributes in simple cases, e.g. size_t __attribute__ ((noinline)) test_parmsz_internal3 (size_t sz1, size_t sz2, double obj[sz1][sz2]) { return __builtin_dynamic_object_size (obj, 0); } or __attribute__ ((noinline, access (read_only, 2, 1))) int foo(int n, int buf[n]) { buf[n] = 1; return __builtin_dynamic_object_size(buf, 0); } int main() { int n = 10; int buf[n]; return foo(n, buf); } Referenced Bugs: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104970 [Bug 104970] [12 Regression] ICE in execute_todo, at passes.cc:2133 since r12-6480-gea19c8f33a3a8d2b
next reply other threads:[~2023-03-29 11:14 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-03-29 11:14 siddhesh at gcc dot gnu.org [this message] 2023-03-30 22:04 ` [Bug tree-optimization/109334] " muecker at gwdg dot de 2023-03-31 12:27 ` siddhesh at gcc dot gnu.org 2023-10-29 6:48 ` cvs-commit at gcc dot gnu.org 2023-10-29 7:29 ` sjames at gcc dot gnu.org 2024-05-07 7:40 ` 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-109334-4@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: linkBe 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).