From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 213053858C53; Sat, 18 May 2024 13:48:19 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 213053858C53 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1716040099; bh=nh7ebicK0ycj5YBB7xP8FUt26w370BlxIwPgVwtFW9A=; h=From:To:Subject:Date:In-Reply-To:References:From; b=N+5a+wiuKKhbE1thSrsz8+biFe3CHoIeq9cxR9Kw0c6oVoZGJvxnxO5ahkvhTDnoQ lTClOdhzuI3Bn3W2XSY9baFiyTHL5FDUz4ofvCjNc3tjLDM1FuUX5mRmWazwMXP1C7 IeVFFu7NRzVZS91DOYE6tKGKNE/+2N0Q/O//EZEg= From: "ebotcazou at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug ada/115106] [15 regression] SEGV in sem_elab.internal_representation.nts_map.mutate_and_rehash Date: Sat, 18 May 2024 13:48:18 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: ada X-Bugzilla-Version: 15.0 X-Bugzilla-Keywords: build, ice-on-valid-code X-Bugzilla-Severity: normal X-Bugzilla-Who: ebotcazou at gcc dot gnu.org X-Bugzilla-Status: RESOLVED X-Bugzilla-Resolution: FIXED X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: 15.0 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_status resolution 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=3D115106 Eric Botcazou changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #6 from Eric Botcazou --- > as of r15-644, Ada bootstrap succeeded on i686-darwin9 and 17. Great! > I do not known whether that means the issue is actually fixed by recent A= da > commits, or that it's now just become latent. Ada commits have nothing to do with it though, the breakage and the probable fix both came from recent optimization changes.=