public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ebotcazou at gcc dot gnu.org" <gcc-bugzilla@gcc.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	[thread overview]
Message-ID: <bug-115106-4-8tZdiyQogy@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-115106-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115106

Eric Botcazou <ebotcazou at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|---                         |FIXED

--- Comment #6 from Eric Botcazou <ebotcazou at gcc dot gnu.org> ---
> 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 Ada
> 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.

  parent reply	other threads:[~2024-05-18 13:48 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-15 15:09 [Bug ada/115106] New: " ro at gcc dot gnu.org
2024-05-15 17:16 ` [Bug ada/115106] " rguenth at gcc dot gnu.org
2024-05-15 21:17 ` ro at gcc dot gnu.org
2024-05-16  9:14 ` ebotcazou at gcc dot gnu.org
2024-05-16 11:57 ` iains at gcc dot gnu.org
2024-05-16 11:58 ` iains at gcc dot gnu.org
2024-05-18 11:21 ` iains at gcc dot gnu.org
2024-05-18 13:48 ` ebotcazou at gcc dot gnu.org [this message]
2024-05-18 17:21 ` iains at gcc dot gnu.org
2024-05-18 18:06 ` ebotcazou at gcc dot gnu.org
2024-05-21  8:56 ` ro at CeBiTec dot Uni-Bielefeld.DE

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-115106-4-8tZdiyQogy@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).