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/114710] too late finalization of temporary object
Date: Thu, 13 Jun 2024 13:33:55 +0000	[thread overview]
Message-ID: <bug-114710-4-eCI9XSifvr@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-114710-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #4 from GCC Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Marc Poulhi?s <dkm@gcc.gnu.org>:

https://gcc.gnu.org/g:916a0f026e1516de4608b308cd7e4b68b8e562bb

commit r15-1264-g916a0f026e1516de4608b308cd7e4b68b8e562bb
Author: Eric Botcazou <ebotcazou@adacore.com>
Date:   Tue Apr 23 19:54:32 2024 +0200

    ada: Fix fallout of previous finalization change

    Now that Is_Finalizable_Transient only looks at the renamings coming from
    nontransient objects serviced by transient scopes, it must find the object
    ultimately renamed by them through a chain of renamings.

    gcc/ada/

            PR ada/114710
            * exp_util.adb (Find_Renamed_Object): Recurse if the renamed object
            is itself a renaming.

  parent reply	other threads:[~2024-06-13 13:33 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-13 17:09 [Bug ada/114710] New: Temporary object finalized too late jhb.chat at gmail dot com
2024-04-20 15:49 ` [Bug ada/114710] temporary " ebotcazou at gcc dot gnu.org
2024-04-21  7:29 ` ebotcazou at gcc dot gnu.org
2024-06-13 13:33 ` [Bug ada/114710] too late finalization of temporary object cvs-commit at gcc dot gnu.org
2024-06-13 13:33 ` cvs-commit at gcc dot gnu.org [this message]
2024-06-13 13:34 ` cvs-commit at gcc dot gnu.org
2024-06-13 17:27 ` 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-114710-4-eCI9XSifvr@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).