public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "zsojka at seznam dot cz" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/112411] ICE: SIGSEGV with --param=min-nondebug-insn-uid=2147483647 on powerpc64le-unknown-linux-gnu Date: Thu, 30 Nov 2023 08:32:16 +0000 [thread overview] Message-ID: <bug-112411-4-sLGv5fs6do@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-112411-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112411 --- Comment #5 from Zdenek Sojka <zsojka at seznam dot cz> --- Thank you for the evaluation. I am not reporting ICEs (assertion / checking failures) due to overflows caused by extreme --param values: - this param is typically causing ICEs due to insn UID overflow - params affecting inlining or unrolling often cause ICEs due to function::last_clique wraparound (it's 16bit uint) - generally, I am trying to consider if a real-world scenario could trigger the ICE This is different, since there is no assertion or checking failure, but a segmentation fault; that is uncommon.
next prev parent reply other threads:[~2023-11-30 8:32 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-11-06 18:30 [Bug target/112411] New: " zsojka at seznam dot cz 2023-11-07 8:37 ` [Bug target/112411] " rguenth at gcc dot gnu.org 2023-11-07 8:55 ` linkw at gcc dot gnu.org 2023-11-07 11:02 ` rsandifo at gcc dot gnu.org 2023-11-30 2:35 ` aoliva at gcc dot gnu.org 2023-11-30 8:32 ` zsojka at seznam dot cz [this message] 2023-11-30 8:39 ` rguenther at suse dot de 2023-12-06 17:47 ` jakub at gcc dot gnu.org 2023-12-06 18:19 ` jakub at gcc dot gnu.org 2023-12-06 18:51 ` jakub at gcc dot gnu.org 2023-12-07 7:56 ` [Bug middle-end/112411] " rguenth at gcc dot gnu.org 2023-12-08 7:33 ` cvs-commit at gcc dot gnu.org 2023-12-08 8:01 ` cvs-commit at gcc dot gnu.org 2023-12-08 8:01 ` jakub 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-112411-4-sLGv5fs6do@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).