public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Simon Wright <simon@pushface.org>
To: Arnaud Charlet <charlet@adacore.com>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] PR ada/66205 gnatbind generates invalid code when finalization is enabled in restricted runtime
Date: Sat, 19 Dec 2015 22:05:00 -0000	[thread overview]
Message-ID: <F37044CA-476B-488D-8C3C-EB6E0DE799FA@pushface.org> (raw)
In-Reply-To: <20151112100205.GA9491@adacore.com>

On 12 Nov 2015, at 10:02, Arnaud Charlet <charlet@adacore.com> 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?
> 
> The proper patch for PR ada/66242 hasn't been committed yet (it's pending),
> so I'd rather review the situation once PR ada/66242 is dealt with.
> 
> I'm not convinced at all that your patch is the way to go, so I'd rather
> consider it only after PR ada/66242 is solved properly.

Looks as though PR ada/66242 has been sorted out.

Since we can now *compile* code that is built with finalization enabled in a restricted runtime, but we can't *bind* it, could we take another look at this? the patch I provided in this thread still applies at snapshot 20151213 with minor offsets (8).

  reply	other threads:[~2015-12-19 22:05 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 [this message]
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=F37044CA-476B-488D-8C3C-EB6E0DE799FA@pushface.org \
    --to=simon@pushface.org \
    --cc=charlet@adacore.com \
    --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).