public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Gary Dismukes <dismukes@adacore.com>
To: Richard Wai <richard@annexi-strayline.com>
Cc: gcc-patches@gcc.gnu.org, Eric Botcazou <ebotcazou@adacore.com>,
	Arnaud Charlet <charlet@adacore.com>,
	Stephen Baird <baird@adacore.com>
Subject: Re: [PATCH 2/2 v2] Ada: Finalization of constrained subtypes of unconstrained synchronized private extensions
Date: Wed, 13 Sep 2023 21:37:09 +0000	[thread overview]
Message-ID: <20230913213709.GA1074648@adacore.com> (raw)

Hi Richard,

I hope you're doing well.

I'm just following up on the patch (second version) that you sent us
recently for the problem you ran into with the generation of the
address finalization routine for synchronized private extensions.

Thanks very much for finding this fix and submitting your patch.
Your patch looks good, and we'll look into applying that to the
compiler, though no guarantees about when it will be added.  

Best regards,
  Gary Dismukes


             reply	other threads:[~2023-09-13 21:37 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-13 21:37 Gary Dismukes [this message]
2023-09-15 16:38 ` Gary Dismukes
     [not found]   ` <010d018aa45631b4-d2c02a5f-44ef-4dbe-b8c1-bd53686aff72-000000@ca-central-1.amazonses.com>
2023-09-18 13:43     ` [PATCH 2/2 v3] " Arnaud Charlet
2023-09-19  3:35       ` Richard Wai
2023-09-19 12:08         ` [COMMITTED] ada: TSS finalize address subprogram generation for constrained Marc Poulhiès
  -- strict thread matches above, loose matches on Subject: below --
2023-08-10  4:55 [PATCH 1/2] Ada: Synchronized private extensions are always limited Richard Wai
2023-08-23 14:24 ` [PATCH 2/2 v2] Ada: Finalization of constrained subtypes of unconstrained synchronized private extensions Richard Wai

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=20230913213709.GA1074648@adacore.com \
    --to=dismukes@adacore.com \
    --cc=baird@adacore.com \
    --cc=charlet@adacore.com \
    --cc=ebotcazou@adacore.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=richard@annexi-strayline.com \
    /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).