public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "law at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/115220] [15 Regression] RISC-V: newlib targets ICE during sink pass triggered in verify_ssa Date: Sat, 25 May 2024 02:03:36 +0000 [thread overview] Message-ID: <bug-115220-4-BuMzRq5pEH@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-115220-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115220 Jeffrey A. Law <law at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Ever confirmed|0 |1 Status|UNCONFIRMED |NEW CC| |law at gcc dot gnu.org, | |rguenth at gcc dot gnu.org Last reconfirmed| |2024-05-25 Target|riscv |riscv,fr30 --- Comment #5 from Jeffrey A. Law <law at gcc dot gnu.org> --- It's a generic problem. Almost certainly caused by the recent changes to the sinking code. It can be triggered (for example) on the fr30-elf port with -Os on this trivial testcase: extern char **environ; static char ***p_environ = &environ; int _setenv_r (const char *name, const char *value) { register char *C; int offset; for (C = (*p_environ)[offset]; (*C = *name++) && *C != '='; ++C); for (*C++ = '='; (*C++ = *value++) != 0;); return 0; }
next prev parent reply other threads:[~2024-05-25 2:03 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-05-24 23:36 [Bug target/115220] New: [15] " ewlu at rivosinc dot com 2024-05-24 23:43 ` [Bug tree-optimization/115220] " pinskia at gcc dot gnu.org 2024-05-25 0:12 ` [Bug tree-optimization/115220] [15 Regression] " ewlu at rivosinc dot com 2024-05-25 0:13 ` ewlu at rivosinc dot com 2024-05-25 0:26 ` pinskia at gcc dot gnu.org 2024-05-25 2:03 ` law at gcc dot gnu.org [this message] 2024-05-27 6:55 ` [Bug tree-optimization/115220] [15 Regression] RISC-V: newlib targets ICE during sink pass triggered in verify_ssa (since r15-815-g5b9b3bae33cae7?) rguenth at gcc dot gnu.org 2024-05-27 7:39 ` rguenth at gcc dot gnu.org 2024-05-27 10:45 ` cvs-commit at gcc dot gnu.org 2024-05-27 10:46 ` 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-115220-4-BuMzRq5pEH@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).