From: Arnaud Charlet <charlet@adacore.com>
To: Simon Wright <simon@pushface.org>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] PR ada/66205 gnatbind generates invalid code when finalization is enabled in restricted runtime
Date: Tue, 05 Dec 2017 18:09:00 -0000 [thread overview]
Message-ID: <20171205180915.GA21842@adacore.com> (raw)
In-Reply-To: <B1D23A9E-1B6B-47AD-90D8-138B3A162507@pushface.org>
> I've come up with a considerably simpler patch, which merely causes the
> procedure adafinal to be generated with a null body if the restriction
> No_Task_Termination is set (note, this restriction is part of the
> Ravenscar profile; if tasks can't terminate, program level finalization
> can't happen [ARM 10.2(25), "When the environment task completes
> (normally or abnormally), it waits for the termination of all such tasks,
> and then finalizes any remaining objects of the partition."]
>
> I've bootstrapped the compiler (x86_64-apple-darwin15), and "make
> check-ada" produces the same results with and without the patch (the same 3
> FAILs occur in both, in gnat.sum). For the arm-eabi compiler, I
> successfully make and run builds for an STM32F4 target without exception
> propagation but with and without finalization.
That's a much simpler and better approach indeed.
OK to commit.
> gcc/ada/Changelog:
>
> 2017-12-05 Simon Wright <simon@pushface.org>
>
> PR ada/66205
> * bindgen.adb (Gen_AdaFinal): If the restriction
> No_Task_Termination is present, generate a null body.
>
next prev parent reply other threads:[~2017-12-05 18:09 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
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 [this message]
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=20171205180915.GA21842@adacore.com \
--to=charlet@adacore.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=simon@pushface.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).