Simon,
Unfortunately we've discovered that your patch is causing unexpected
consequences and break e.g. testing of ravenscar application, where
although the Ada RM requires no task termination, for practical
purposes, waiting for terminating task is something we rely upon for
automatic testing,
> 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
On 7 Mar 2017, at 16:20, Simon Wright wrote:
>
> On 19 Dec 2015, at 22:05, Simon Wright wrote:
>>
>> On 12 Nov 2015, at 10:02, Arnaud Charlet wrote:
>>>
> This situation arises, for example, with an embedded RTS that
>
On 19 Dec 2015, at 22:05, Simon Wright wrote:
>
> On 12 Nov 2015, at 10:02, Arnaud Charlet wrote:
>>
This situation arises, for example, with an embedded RTS that
incorporates the
Ada 2012 generalized container iterators.
>>>
>>> I
On 12 Nov 2015, at 10:02, Arnaud Charlet 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
On 11 Nov 2015, at 19:43, Simon Wright 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
> > 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?
The proper patch for PR ada/66242
I’ve updated the original patch, which was built against 5.1.0 on
x64_64-apple-darwin13, this patch is against 6.0.0-20151101 on
x86_64-apple-darwin15.
--
If the RTS in use is "configurable" (I believe this is the same in this context
as "restricted") and includes finalization,