From: Simon Wright <simon@pushface.org>
To: gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] PR ada/66205 gnatbind generates invalid code when finalization is enabled in restricted runtime
Date: Thu, 12 Nov 2015 08:56:00 -0000 [thread overview]
Message-ID: <666D196C-C248-45B3-A20F-138CE6B00457@pushface.org> (raw)
In-Reply-To: <E8542217-EDC5-48AE-B087-F49528CF4AD1@pushface.org>
On 11 Nov 2015, at 19:43, Simon Wright <simon@pushface.org> wrote:
> This situation arises, for example, with an embedded RTS that incorporates the
> Ada 2012 generalized container iterators.
I should add, this PR is the “other half” of PR ada/66242, which is fixed in GCC 6; so
please can it be reviewed?
I didn’t make it plain that the comment I’ve put in the first hunk,
-- For restricted run-time libraries (ZFP and Ravenscar) tasks
-- are non-terminating, so we do not want finalization.
is lifted from the unpatched code at line 480, where it relates to the use of
Configurable_Run_Time_On_Target for this purpose.
next prev parent reply other threads:[~2015-11-12 8:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-15 16:31 Simon Wright
2015-11-11 19:43 ` Simon Wright
2015-11-12 8:56 ` Simon Wright [this message]
2015-11-12 10:02 ` Arnaud Charlet
2015-12-19 22:05 ` Simon Wright
2017-03-07 16:20 ` Simon Wright
2017-12-05 17:16 ` Simon Wright
2017-12-05 18:09 ` Arnaud Charlet
2017-12-19 8:41 ` Arnaud Charlet
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=666D196C-C248-45B3-A20F-138CE6B00457@pushface.org \
--to=simon@pushface.org \
--cc=gcc-patches@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).