public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <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: Wed, 06 Dec 2023 18:19:45 +0000 [thread overview] Message-ID: <bug-112411-4-1nKDwMQJxM@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 Jakub Jelinek <jakub at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |vmakarov at gcc dot gnu.org --- Comment #8 from Jakub Jelinek <jakub at gcc dot gnu.org> --- Note, on void foo (void) { } ./cc1 -quiet --param min-nondebug-insn-uid=0x2aaaa000 pr112411.c still works but is fairly slow (various passes index arrays by INSN_UID and if the uids are huge, it takes a lot of memory and compile time to clear them). But ./cc1 -quiet --param min-nondebug-insn-uid=0x2aaaaaaa a.c cc1: out of memory allocating 18446744065119617112 bytes after a total of 1626112 bytes Seems lra does some vec handling by hand and uses an int variable for it: lra.cc (check_and_expand_insn_recog_data): lra_insn_recog_data_len = index * 3 / 2 + 1; Shall we change lra_insn_recog_data_len to size_t (and tweak comparisons to avoid signed vs. unsigned compares)? Or at least adjust the above such that the computation is say done in unsigned HOST_WIDE_INT and use INT_MAX for lra_insn_recog_data_len on overflow rather than negative value (including UB at compile time)? With the following patch it compiles even with ./cc1 -quiet --param min-nondebug-insn-uid=0x40000000 a.c but my 32GB RAM + 24GB swap was almost full with that. --- gcc/params.opt.jj 2023-11-02 07:49:18.010852541 +0100 +++ gcc/params.opt 2023-12-06 18:55:57.045420935 +0100 @@ -779,7 +779,7 @@ Common Joined UInteger Var(param_min_loo The minimum threshold for probability of semi-invariant condition statement to trigger loop split. -param=min-nondebug-insn-uid= -Common Joined UInteger Var(param_min_nondebug_insn_uid) Param +Common Joined UInteger Var(param_min_nondebug_insn_uid) Param IntegerRange(0, 1073741824) The minimum UID to be used for a nondebug insn. -param=min-size-for-stack-sharing= --- gcc/lra.cc.jj 2023-12-05 13:17:29.642260866 +0100 +++ gcc/lra.cc 2023-12-06 19:14:52.117499420 +0100 @@ -764,11 +764,13 @@ static void check_and_expand_insn_recog_data (int index) { int i, old; + HOST_WIDE_INT len; if (lra_insn_recog_data_len > index) return; old = lra_insn_recog_data_len; - lra_insn_recog_data_len = index * 3 / 2 + 1; + len = index * HOST_WIDE_INT_C (3) / 2 + 1; + lra_insn_recog_data_len = MIN (len, INT_MAX); lra_insn_recog_data = XRESIZEVEC (lra_insn_recog_data_t, lra_insn_recog_data, lra_insn_recog_data_len);
next prev parent reply other threads:[~2023-12-06 18:19 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 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 [this message] 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-1nKDwMQJxM@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).