From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 63E443858C56; Tue, 5 Mar 2024 10:36:14 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 63E443858C56 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1709634974; bh=kDOm5VjDPx4ml8woh3PQiXIhWcKO7dGyVMtuKN8FIJY=; h=From:To:Subject:Date:In-Reply-To:References:From; b=k4ipYBjEnFIaG19bouQ3yd81Yf2UxrfD96NJa9gB9LLBZnX6BDPHlmprJDoK/g+XV uVRTwMza6MCKUmHkZd9DHRjsRp6Soz6bm3F11dmIyNNjd2fWJdxfnnsHjFsZLDGeMa BwpNgUXwTi5D7ZyrCpFpOW/wj4DG64t3BlDgMqB8= From: "sarah.kriesch at opensuse dot org" To: gcc-bugs@gcc.gnu.org Subject: [Bug rtl-optimization/101523] Huge number of combine attempts Date: Tue, 05 Mar 2024 10:36:13 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: rtl-optimization X-Bugzilla-Version: 12.0 X-Bugzilla-Keywords: compile-time-hog, memory-hog X-Bugzilla-Severity: normal X-Bugzilla-Who: sarah.kriesch at opensuse dot org X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: segher at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: 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=3D101523 --- Comment #15 from Sarah Julia Kriesch --- (In reply to Segher Boessenkool from comment #13) > (In reply to Sarah Julia Kriesch from comment #12) > A bigger case of what? What do you mean? Not only one software package is affected by this bug. "Most" software buil= ds are affected. As Andreas mentioned correctly, the fix is also beneficial for other projects/target software. There are so many packages with customized memory settings for s390x at openSUSE, and the Maintainers can only shake their head about this behaviou= r. But let's progress step by step. I have luck, that also IBM customers are raising questions regarding that n= ow.=