From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id C70B0385DC24; Thu, 16 Apr 2020 17:20:10 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org C70B0385DC24 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1587057610; bh=dRy8pS67XuhurAPSVBwhRNfoEfAnsU3exGIrMRoXLgU=; h=From:To:Subject:Date:In-Reply-To:References:From; b=LL/LuP7ozIf9Hi45Y72CSGOJlcNFRKje3vgWrXgJKQxwelQNbQnPQfeedKUt710H3 5e83+12NWY26Pn/BhDD2fO+NiLbb/DQOui5646hGm2uiu1E7xBUOKbJekUu9tyy3AA 38C45tUzcyqB+xUvDQCRShI3hlMrzlHxPWanX1Vg= From: "gcc at octaforge dot org" To: gcc-bugs@gcc.gnu.org Subject: [Bug target/94611] gccgo hangs (infinite loop) on complex projects, seemingly in simplify-rtx.c/simplify_plus_minus Date: Thu, 16 Apr 2020 17:20:10 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: target X-Bugzilla-Version: 9.3.0 X-Bugzilla-Keywords: compile-time-hog X-Bugzilla-Severity: normal X-Bugzilla-Who: gcc at octaforge dot 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: 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 X-BeenThere: gcc-bugs@gcc.gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gcc-bugs mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 16 Apr 2020 17:20:10 -0000 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D94611 --- Comment #9 from Daniel Kolesa --- it finishes with -fno-var-tracking, though it does take up a few gigs of me= mory and takes a while, this is consistent with the default behavior on x86_64 w= here it does the same thing.=