public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub 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: Mon, 21 Mar 2022 18:18:01 +0000	[thread overview]
Message-ID: <bug-104970-4-zYuBDVhXnK@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 #6 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
I can't speak for Siddhesh, but at least the testcase coverage in r12-6480
only covered the access attribute.  So perhaps the fix could be to just limit
to that case if it is possible easily to differentiate that from the other
cases.
And certainly if it uses TYPE_SIZE_UNIT for something it needs to punt if it
isn't a constant (or perhaps POLY_INT_CST), because the trees mentioned in
there can't be reliably used during objsz1.

  parent reply	other threads:[~2022-03-21 18:18 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 [this message]
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
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-zYuBDVhXnK@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).