From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id B05EA385843B; Wed, 24 Jan 2024 08:53:36 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org B05EA385843B DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1706086416; bh=6+LGzUS3Wj8ys7VAA7+rZPGdEGN8q3nY8ceqYUSLNBA=; h=From:To:Subject:Date:In-Reply-To:References:From; b=nfIAqHOg37lPkxE0g7gEXZvEPZa1AKxrY0aMIty7q6sNUznmvWUU2MIkxp3vRewQ/ hE5M045JE4z6cwo1OSS8q2A+Os5Y7xX8v2uIZ4r8UBe/vR/swtqDrjO5Z6r0KC97uN 8SL2Mk2NNn7WL1Cy/21w33KWsOgQ9l1WXuDNa8f0= From: "rdapp at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug other/113575] [14 Regression] memory hog building insn-opinit.o (i686-linux-gnu -> riscv64-linux-gnu) Date: Wed, 24 Jan 2024 08:53:24 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: other X-Bugzilla-Version: 14.0 X-Bugzilla-Keywords: build, memory-hog X-Bugzilla-Severity: normal X-Bugzilla-Who: rdapp at gcc dot gnu.org X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 List-Id: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D113575 Robin Dapp changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |rdapp at gcc dot gnu.org --- Comment #5 from Robin Dapp --- Yes, this is a known issue and it's due to our large number of patterns.=20 Contrary to insn-emit insn-opinit cannot be split that easily. It would probably need a tree-like approach or similar. I wouldn't see this as a regression in the classical sense as we just have = many more patterns because of the vector extension. Is increasing the available memory an option in the meantime or does this urgently require fixing?=