Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Simon Marchi via Gdb-patches <gdb-patches@sourceware.org>
To: Tom Tromey <tom@tromey.com>,
	Simon Marchi via Gdb-patches <gdb-patches@sourceware.org>
Subject: Re: [PATCH 2/4] gdbsupport: add array_view copy function
Date: Tue, 16 Nov 2021 16:56:13 -0500	[thread overview]
Message-ID: <90ddca61-ea64-b354-6fb4-99ab607a43d6@efficios.com> (raw)
In-Reply-To: <87h7cbesar.fsf@tromey.com>

On 2021-11-16 3:53 p.m., Tom Tromey wrote:
>>>>>> "Simon" == Simon Marchi via Gdb-patches <gdb-patches@sourceware.org> writes:
>
> Simon> An assertion was recently added to array_view::operator[] to ensure we
> Simon> don't do out of bounds accesses.  However, when the array_view is copied
> Simon> to or from using memcpy, it bypasses this safety.
>
> Simon> To address this, add a `copy` free function that copies data from an
> Simon> array view to another.  It ensures that the destination and source array
> Simon> views have the same size and element size, which prevents any kind of
> Simon> overflow in the source and in the destination.
>
> In C++20 I think we could use std::copy by having the array view
> iterators implement the contiguous_iterator concept.  So, maybe a
> comment to this effect would be good.

Do you mean we could use std::copy to implement this copy function,
instead of using memcpy, and that would deal with the details of copying
in the most efficient manner?

If I read cppreference correctly [1], std::copy is available before
C++20, it's just that in C++20 it has been made constexpr.  So I could
maybe give it a try, instead of using memcpy.

[1] https://en.cppreference.com/w/cpp/algorithm/copy

> Though maybe in C++20 we would want to switch from array_view to
> std::span.

Ack.

Simon

  reply	other threads:[~2021-11-16 21:56 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-08 21:06 [PATCH 1/4] gdb: fix length of array view returned by some value_contents functions Simon Marchi via Gdb-patches
2021-11-08 21:06 ` [PATCH 2/4] gdbsupport: add array_view copy function Simon Marchi via Gdb-patches
2021-11-08 21:11   ` Simon Marchi via Gdb-patches
2021-11-16 20:54     ` Tom Tromey
2021-11-16 20:53   ` Tom Tromey
2021-11-16 21:56     ` Simon Marchi via Gdb-patches [this message]
2021-11-17  0:20       ` Tom Tromey
2021-11-18 20:07         ` Simon Marchi
2021-11-08 21:06 ` [PATCH 3/4] gdb: make extract_integer take an array_view Simon Marchi via Gdb-patches
2021-11-08 21:06 ` [PATCH 4/4] gdb: trivial changes to use array_view Simon Marchi via Gdb-patches
2021-11-16 20:41 ` [PATCH 1/4] gdb: fix length of array view returned by some value_contents functions Tom Tromey
2021-11-16 21:40   ` Simon Marchi

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=90ddca61-ea64-b354-6fb4-99ab607a43d6@efficios.com \
    --to=gdb-patches@sourceware.org \
    --cc=simon.marchi@efficios.com \
    --cc=tom@tromey.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