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/106037] internal error with Aggregate aspect on array type Date: Wed, 13 Mar 2024 15:40:39 +0000 [thread overview] Message-ID: <bug-106037-4-vgX2pS70FL@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-106037-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106037 Eric Botcazou <ebotcazou at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Target Milestone|--- |13.3 Summary|ICE with Aggregate aspect |internal error with | |Aggregate aspect on array | |type Resolution|--- |FIXED --- Comment #5 from Eric Botcazou <ebotcazou at gcc dot gnu.org> --- commit ec48b99c24a422bf97af91e82203d23b69094e7c Author: Marc Poulhiès <poulhies@adacore.com> Date: Wed Mar 8 20:39:45 2023 +0100 ada: Fix error message for Aggregate aspect The error message was wrongly using % instead of & in the format string, causing the displayed message to refer to incorrect names in some cases. gcc/ada/ * sem_ch13.adb (Check_Aspect_At_Freeze_Point): fix format string, use existing local Ident. commit 3da0e4ae25f15949f87e74aa96a03b47e51a9ff3 Author: Marc Poulhiès <poulhies@adacore.com> Date: Mon Mar 6 12:15:13 2023 +0100 ada: Fix (again) incorrect handling of Aggregate aspect Previous fix stopped the processing of the Aggregate aspect early, skipping the call to Record_Rep_Item, making later call to Resolve_Container_Aggregate fail. Also, the previous fix would not handle correctly the case where the type is private and the check for non-array type can only be done at the freeze point with the full type. Adapt the resolving of the aspect when the input is not correct and the parameters can't be resolved. gcc/ada/ * sem_ch13.adb (Analyze_One_Aspect): Call Record_Rep_Item. (Check_Aspect_At_Freeze_Point): Check the aspect is specified on non-array type only... (Analyze_One_Aspect): ... instead of doing it too early here. * sem_aggr.adb (Resolve_Container_Aggregate): Do nothing in case the parameters failed to resolve. commit fd694822ca6eda8b08fea10fcabdb0ad508a963e Author: Marc Poulhiès <poulhies@adacore.com> Date: Tue Feb 28 17:10:29 2023 +0100 ada: Fix incorrect handling of Aggregate aspect This change fixes 2 incorrect handlings of the aspect. The arguments are now correctly resolved and the aspect is rejected on non array types. gcc/ada/ * sem_ch13.adb (Analyze_One_Aspect): Mark Aggregate aspect as needing delayed resolution and reject the aspect on non-array type.
prev parent reply other threads:[~2024-03-13 15:40 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-06-20 22:38 [Bug ada/106037] New: ICE with Aggregate aspect jesper.quorning at gmail dot com 2022-07-01 11:07 ` [Bug ada/106037] " ebotcazou at gcc dot gnu.org 2022-07-02 16:16 ` p.p11 at orange dot fr 2024-03-13 15:11 ` simon at pushface dot org 2024-03-13 15:40 ` 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-106037-4-vgX2pS70FL@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: linkBe 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).