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 middle-end/111818] [11/12/13/14 Regression] ICE with __builtin_memcpy with volatile and constants Date: Sun, 15 Oct 2023 01:47:21 +0000 [thread overview] Message-ID: <bug-111818-4-Tudsg4GzR0@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-111818-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111818 Andrew Pinski <pinskia at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Known to work| |4.9.1 Known to fail| |10.1.0, 5.1.0 Target Milestone|--- |11.5 Ever confirmed|0 |1 Last reconfirmed| |2023-10-15 Summary|GCC: 14: internal compiler |[11/12/13/14 Regression] |error: tree check: expected |ICE with __builtin_memcpy |tree that contains 'decl |with volatile and constants |common' structure, have | |'integer_cst' in | |tree_could_trap_p, at | |tree-eh.cc:2733 | Status|UNCONFIRMED |NEW --- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> --- Confirmed. Even though GCC 11.x and 12.x and 13.x don't ICE without checking enabled. The IR is still invalid: _9 ={v} MEM <unsigned int> [(char * {ref-all})&305419896]; That is just wrong.
next prev parent reply other threads:[~2023-10-15 1:47 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-10-15 1:38 [Bug c/111818] New: GCC: 14: internal compiler error: tree check: expected tree that contains 'decl common' structure, have 'integer_cst' in tree_could_trap_p, at tree-eh.cc:2733 141242068 at smail dot nju.edu.cn 2023-10-15 1:47 ` pinskia at gcc dot gnu.org [this message] 2023-10-16 6:59 ` [Bug middle-end/111818] [11/12/13/14 Regression] ICE with __builtin_memcpy with volatile and constants rguenth at gcc dot gnu.org 2023-10-17 6:26 ` cvs-commit at gcc dot gnu.org 2023-10-17 6:27 ` [Bug middle-end/111818] [11/12/13 " rguenth at gcc dot gnu.org 2023-11-10 14:24 ` cvs-commit at gcc dot gnu.org 2023-11-27 13:09 ` [Bug middle-end/111818] [11/12 " cvs-commit at gcc dot gnu.org 2023-12-15 12:18 ` [Bug middle-end/111818] [11 " cvs-commit at gcc dot gnu.org 2023-12-15 12:22 ` 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-111818-4-Tudsg4GzR0@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).