public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
* [gcc/devel/rust/master] libproc_macro: Fix literal drop function
@ 2023-05-02  7:09 Thomas Schwinge
  0 siblings, 0 replies; only message in thread
From: Thomas Schwinge @ 2023-05-02  7:09 UTC (permalink / raw)
  To: gcc-cvs

https://gcc.gnu.org/g:aa108c21644dfa793a39b59851531f5edf4d2196

commit aa108c21644dfa793a39b59851531f5edf4d2196
Author: Pierre-Emmanuel Patry <pierre-emmanuel.patry@embecosm.com>
Date:   Fri Apr 21 12:00:08 2023 +0200

    libproc_macro: Fix literal drop function
    
    Fix drop function by changing the delete operator to delete[] in order
    to avoid undefined behaviors.
    
    ChangeLog:
    
            * libgrust/libproc_macro/literal.cc (Literal::drop): Change
            delete operator to delete[].
    
    Signed-off-by: Pierre-Emmanuel Patry <pierre-emmanuel.patry@embecosm.com>

Diff:
---
 libgrust/libproc_macro/literal.cc | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/libgrust/libproc_macro/literal.cc b/libgrust/libproc_macro/literal.cc
index 221c57a0da5..d4977533a90 100644
--- a/libgrust/libproc_macro/literal.cc
+++ b/libgrust/libproc_macro/literal.cc
@@ -32,11 +32,11 @@ Literal::drop (Literal *lit)
   switch (lit->tag)
     {
     case STRING:
-      delete lit->payload.string_payload.data;
+      delete[] lit->payload.string_payload.data;
       lit->payload.string_payload.len = 0;
       break;
     case BYTE_STRING:
-      delete lit->payload.byte_string_payload.data;
+      delete[] lit->payload.byte_string_payload.data;
       lit->payload.byte_string_payload.size = 0;
       break;
     case CHAR:

^ permalink raw reply	[flat|nested] only message in thread

only message in thread, other threads:[~2023-05-02  7:09 UTC | newest]

Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2023-05-02  7:09 [gcc/devel/rust/master] libproc_macro: Fix literal drop function Thomas Schwinge

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).