public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Marc Poulhi?s <dkm@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org
Subject: [gcc r13-4288] ada: Add assertion for the implementation of storage models
Date: Thu, 24 Nov 2022 10:12:21 +0000 (GMT)	[thread overview]
Message-ID: <20221124101221.ADCFB3858296@sourceware.org> (raw)

https://gcc.gnu.org/g:7f77aa6b2f04781faa78373add11538d276c8ae4

commit r13-4288-g7f77aa6b2f04781faa78373add11538d276c8ae4
Author: Eric Botcazou <ebotcazou@adacore.com>
Date:   Tue Nov 22 13:03:00 2022 +0100

    ada: Add assertion for the implementation of storage models
    
    We cannot generate a call to memset for an aggregate with an Others choice
    when the target of the assignment has a storage model with Copy_To routine.
    
    gcc/ada/
    
            * gcc-interface/trans.cc (gnat_to_gnu) <N_Assignment_Statement>: Add
            assertion that memset is not supposed to be used when the target has
            a storage model with Copy_To routine.

Diff:
---
 gcc/ada/gcc-interface/trans.cc | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/gcc/ada/gcc-interface/trans.cc b/gcc/ada/gcc-interface/trans.cc
index 1cd621a9377..b9d7c015a73 100644
--- a/gcc/ada/gcc-interface/trans.cc
+++ b/gcc/ada/gcc-interface/trans.cc
@@ -7450,6 +7450,9 @@ gnat_to_gnu (Node_Id gnat_node)
 	  else if (Present (gnat_smo)
 		   && Present (Storage_Model_Copy_To (gnat_smo)))
 	    {
+	      /* We obviously cannot use memset in this case.  */
+	      gcc_assert (!use_memset_p);
+
 	      tree t = remove_conversions (gnu_rhs, false);
 
 	      /* If a storage model load is present on the RHS then instantiate

                 reply	other threads:[~2022-11-24 10:12 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20221124101221.ADCFB3858296@sourceware.org \
    --to=dkm@gcc.gnu.org \
    --cc=gcc-cvs@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).