public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/101478] [11/12/13/14 Regression] ICE with statement expression and offsetof like expression
Date: Sat, 23 Mar 2024 20:14:55 +0000	[thread overview]
Message-ID: <bug-101478-4-cy9mfDZ01o@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-101478-4@http.gcc.gnu.org/bugzilla/>

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

Andrew Pinski <pinskia at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Summary|[11/12/13/14 Regression]    |[11/12/13/14 Regression]
                   |ICE on invalid code:        |ICE with statement
                   |recompute_tree_invariant_fo |expression and offsetof
                   |r_addr_expr                 |like expression
           Priority|P4                          |P3
           Keywords|error-recovery,             |ice-on-valid-code
                   |ice-on-invalid-code         |

--- Comment #4 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
You can make this valid (maybe not runtime defined) GNU C code that ICEs in the
same way:
```
struct obj {
  int n;
  int l;
};
int main() {
  (struct obj *)((char *)(__SIZE_TYPE__)({ 0; }) - (char *)&((struct obj
*)0)->l);
}

```

      parent reply	other threads:[~2024-03-23 20:14 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-16 20:42 [Bug c/101478] New: ICE on invalid code: recompute_tree_invariant_for_addr_expr cnsun at uwaterloo dot ca
2021-08-22  4:42 ` [Bug c/101478] [10/11/12 Regression] " pinskia at gcc dot gnu.org
2022-01-09  0:36 ` pinskia at gcc dot gnu.org
2022-01-20 12:47 ` rguenth at gcc dot gnu.org
2022-06-28 10:45 ` [Bug c/101478] [10/11/12/13 " jakub at gcc dot gnu.org
2023-07-07 10:40 ` [Bug c/101478] [11/12/13/14 " rguenth at gcc dot gnu.org
2024-03-23 20:14 ` pinskia at gcc dot gnu.org [this message]

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-101478-4-cy9mfDZ01o@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).