public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/107976] ICE: SIGSEGV (stack overflow) in emit_case_dispatch_table (stmt.cc:783) with large --param=jump-table-max-growth-ratio-for-speed Date: Wed, 11 Jan 2023 12:06:47 +0000 [thread overview] Message-ID: <bug-107976-4-aGFT2xyX0A@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-107976-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107976 --- Comment #5 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Martin Liska <marxin@gcc.gnu.org>: https://gcc.gnu.org/g:8221efae233e2d5992a79600071dd0a52f1b3c74 commit r13-5104-g8221efae233e2d5992a79600071dd0a52f1b3c74 Author: Martin Liska <mliska@suse.cz> Date: Wed Dec 28 09:11:40 2022 +0100 switch expansion: limit JT growth param values Currently, one can request a huge jump table creation which leads to a non-sensual huge output. Moreover, use auto_vec rather than a stack-allocated array. PR middle-end/107976 gcc/ChangeLog: * params.opt: Limit JT params. * stmt.cc (emit_case_dispatch_table): Use auto_vec.
next prev parent reply other threads:[~2023-01-11 12:06 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-12-05 18:53 [Bug tree-optimization/107976] New: " zsojka at seznam dot cz 2022-12-05 19:11 ` [Bug middle-end/107976] " pinskia at gcc dot gnu.org 2022-12-06 9:31 ` rguenth at gcc dot gnu.org 2022-12-08 9:44 ` marxin at gcc dot gnu.org 2022-12-09 12:20 ` zsojka at seznam dot cz 2022-12-28 9:01 ` marxin at gcc dot gnu.org 2023-01-11 12:06 ` cvs-commit at gcc dot gnu.org [this message] 2023-01-11 12:07 ` marxin 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-107976-4-aGFT2xyX0A@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).