public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ada/113979] [11/12/13/14 regression] bogus error on allocator for array type with Dynamic_Predicate
Date: Thu, 07 Mar 2024 14:27:23 +0000	[thread overview]
Message-ID: <bug-113979-4-RSikRCwSZn@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-113979-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #6 from GCC Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-11 branch has been updated by Eric Botcazou
<ebotcazou@gcc.gnu.org>:

https://gcc.gnu.org/g:b26501b6e310345ad9f6423b3f8b9df178c5e7d9

commit r11-11272-gb26501b6e310345ad9f6423b3f8b9df178c5e7d9
Author: Eric Botcazou <ebotcazou@adacore.com>
Date:   Thu Mar 7 15:05:54 2024 +0100

    Fix bogus error on allocator for array type with Dynamic_Predicate

    This is a regression present on all active branches: the compiler gives
    a bogus error on an allocator for an unconstrained array type declared
    with a Dynamic_Predicate because Apply_Predicate_Check is invoked directly
    on a subtype reference, which it cannot handle.

    This moves the check to the resulting access value (after dereference) like
    in Expand_Allocator_Expression.

    gcc/ada/
            PR ada/113979
            * exp_ch4.adb (Expand_N_Allocator): In the subtype indication case,
            remove call to Apply_Predicate_Check.

    gcc/testsuite/
            * gnat.dg/predicate15.adb: New test.

  parent reply	other threads:[~2024-03-07 14:27 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-18 14:31 [Bug ada/113979] New: Allocation of 2D array fails when Dynamic Predicate applied to type simon at pushface dot org
2024-02-19 12:17 ` [Bug ada/113979] [10/11/12/13/14 regression] bogus error on allocator for type with Dynamic_Predicate ebotcazou at gcc dot gnu.org
2024-02-19 12:17 ` ebotcazou at gcc dot gnu.org
2024-03-04 13:09 ` [Bug ada/113979] [11/12/13/14 " rguenth at gcc dot gnu.org
2024-03-04 13:09 ` rguenth at gcc dot gnu.org
2024-03-07 14:08 ` [Bug ada/113979] [11/12/13/14 regression] bogus error on allocator for array " cvs-commit at gcc dot gnu.org
2024-03-07 14:18 ` cvs-commit at gcc dot gnu.org
2024-03-07 14:22 ` cvs-commit at gcc dot gnu.org
2024-03-07 14:27 ` cvs-commit at gcc dot gnu.org [this message]
2024-03-07 14:28 ` ebotcazou at gcc dot gnu.org

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-113979-4-RSikRCwSZn@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).