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/113195] [13/14 regression] internal error on anonymous access type equality
Date: Tue, 09 Jan 2024 09:32:00 +0000	[thread overview]
Message-ID: <bug-113195-4-HVTZy0bIyO@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-113195-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #5 from Eric Botcazou <ebotcazou at gcc dot gnu.org> ---
https://gcc.gnu.org/g:13f8c71aebc7df388678c52cffbc11db980d8fa0

commit r13-8202-g13f8c71aebc7df388678c52cffbc11db980d8fa0
Author: Eric Botcazou <ebotcazou@adacore.com>
Date:   Tue Jan 9 10:21:51 2024 +0100

    Fix internal error on anonymous access type equality

    This is a small regression present on the mainline and 13 branch, in the
    form of an internal error in gigi on anonymous access type equality.  We
    now need to also accept them for anonymous access types that point to
    compatible object subtypes in the language sense.

    gcc/ada/
            * gcc-interface/utils2.cc (build_binary_op) <EQ_EXPR>: Relax
            assertion for regular pointer types.

    gcc/testsuite/
          * gnat.dg/specs/anon4.ads: New test.

      parent reply	other threads:[~2024-01-09  9:32 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-02  4:07 [Bug ada/113195] New: gnat bug box when comparing access to subtype with access inside record nicolas at debian dot org
2024-01-08  8:38 ` [Bug ada/113195] [13/14 regression] internal error on anonymous access type equality ebotcazou at gcc dot gnu.org
2024-01-08  8:39 ` ebotcazou at gcc dot gnu.org
2024-01-08 14:25 ` rguenth at gcc dot gnu.org
2024-01-09  9:28 ` ebotcazou at gcc dot gnu.org
2024-01-09  9:31 ` ebotcazou at gcc dot gnu.org
2024-01-09  9:32 ` ebotcazou at gcc dot gnu.org [this message]

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-113195-4-HVTZy0bIyO@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).