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/109881] internal error on function returning dynamically-sized type
Date: Thu, 16 Nov 2023 17:43:17 +0000	[thread overview]
Message-ID: <bug-109881-4-4IeqhDr7Ls@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-109881-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #6 from Eric Botcazou <ebotcazou at gcc dot gnu.org> ---
https://gcc.gnu.org/g:c5e1cb7e501350ea339db44ca5a33704d817a6fb

commit r13-8075-gc5e1cb7e501350ea339db44ca5a33704d817a6fb
Author: Eric Botcazou <ebotcazou@adacore.com>
Date:   Thu Nov 16 18:36:44 2023 +0100

    Fix internal error on function returning dynamically-sized type

    This is a tree sharing issue for the internal return type synthesized for
    a function returning a dynamically-sized type and taking an Out or In/Out
    parameter passed by copy.

    gcc/ada/
            * gcc-interface/decl.cc (gnat_to_gnu_subprog_type): Also create a
            TYPE_DECL for the return type built for the CI/CO mechanism.

    gcc/testsuite/
            * gnat.dg/varsize4.ads, gnat.dg/varsize4.adb: New test.
            * gnat.dg/varsize4_pkg.ads: New helper.

  parent reply	other threads:[~2023-11-16 17:43 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-16 22:26 [Bug ada/109881] New: GNAT BUG DETECTED during RTL pass, raised TYPES.UNRECOVERABLE_ERROR gnugcc at marino dot st
2023-05-16 22:32 ` [Bug ada/109881] " gnugcc at marino dot st
2023-05-16 23:41 ` gnugcc at marino dot st
2023-05-18  8:48 ` ebotcazou at gcc dot gnu.org
2023-05-18  8:50 ` [Bug ada/109881] internal error on function returning dynamically-sized array ebotcazou at gcc dot gnu.org
2023-11-16 17:42 ` [Bug ada/109881] internal error on function returning dynamically-sized type ebotcazou at gcc dot gnu.org
2023-11-16 17:43 ` ebotcazou at gcc dot gnu.org [this message]
2023-11-16 17:43 ` ebotcazou at gcc dot gnu.org
2023-11-16 17:44 ` 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-109881-4-4IeqhDr7Ls@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).