From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id AEECF3858D39; Sat, 4 May 2024 13:14:19 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org AEECF3858D39 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1714828459; bh=TTabeMbc0baZ8s/CK4S1a4GpA28rcBmqSc4BXhZelDo=; h=From:To:Subject:Date:In-Reply-To:References:From; b=uMC5po71FwGnBCtXaQ/eREE5xvzAO75ux8yk1iKwNIckFybNBD5bcQYz1DMDc6OT2 /PORX1R2+YXyee0PpVq48aKbuPhj8wGYWN9bQ4hd1MyChSlzzsO93UhpjcNb+nvFtV OCFrjZlBaUf3/Qry2sg+raolYiN7jcbFQMxZqKw0= From: "sarah.kriesch at opensuse dot org" To: gcc-bugs@gcc.gnu.org Subject: [Bug rtl-optimization/101523] Huge number of combine attempts Date: Sat, 04 May 2024 13:14:18 +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: ASSIGNED X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: rguenth 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 #62 from Sarah Julia Kriesch --- (In reply to Segher Boessenkool from comment #61) > (In reply to Sarah Julia Kriesch from comment #60) > > I have to agree with Richard. This problem has been serious for a long = time > > but has been ignored by IBM based on distribution choices. >=20 > What? What does IBM have to do with this? Yes, they are my employer, but > what I decide is best for combine to do is not influenced by them *at all* > (except some times they want me to spend time doing paid work, distracting > me from things that really matter, like combine!) >=20 Then, tell other reasons why my requests in the openSUSE bug report have be= en rejected in the past, and this bug report has been open for 3 years. Perhaps it is helpful to know that IBM has fixed memory issues in PostgreSQL (for openSUSE/upstream) with higher quality via my request with the support= for Red Hat (and faster). > > Anyway, we want to live within the open source community without any Li= nux > > distribution priorities (especially in upstream projects like here). >=20 > No idea what that means either. >=20 There is a reason for founding the Linux Distributions Working Group at the Open Mainframe Project (equality for all Linux Distributions on s390x). SUSE, Red Hat and Canonical have been supporting this idea also (especially based on my own work experience at IBM and the priorities inside). > > Segher, can you specify the failed test cases? Then, it should be possi= ble > > to reproduce and improve that all. In such a collaborative way, we can = also > > achieve a solution. >=20 > What failed test cases? You completely lost me. >=20 This one: (In reply to Segher Boessenkool from comment #57) > (In reply to Richard Biener from comment #56) > PR101523 is a very serious problem, way way way more "P1" than any of the > "my target was inconvenienced by some bad testcases failing now" "P1"s th= ere > are now. Please undo this! (In reply to Segher Boessenkool from comment #61) > We used to do the wrong thing in combine. Now that my fix was reverted, = we > still do. This should be undone soonish, so that I can commit an actual > UNCSE > implementation, which fixes all "regressions" (quotes, because they are n= ot!) > caused by my previous patch, and does a lot more too. It also will allow= us > to remove a bunch of other code from combine, speeding up things a lot mo= re > (things that keep a copy of a set if the dest is used more than once). T= here > has been talk of doing an UNCSE for over twenty years now, so annoying me > enough to get this done is a good result of this whole thing :-) Your fixes should also work with upstream code and the used gcc versions in our/all Linux distributions. I recommend applying tests and merging your fi= xes to at least one gcc version. If you want to watch something about our reasons for creating a collaborati= on between Linux distributions (and upstream projects), you should watch my fi= rst presentation "Collaboration instead of Competition": https://av.tib.eu/media/57010 Hint: The IBM statement came from my former IBM Manager (now your CPO).=