Frama-C-discuss mailing list archives

This page gathers the archives of the old Frama-C-discuss archives, that was hosted by Inria's gforge before its demise at the end of 2020. To search for mails newer than September 2020, please visit the page of the new mailing list on Renater.

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Frama-c-discuss] Warnings for call to memcpy()... why?

Subject: [Frama-c-discuss] Warnings for call to memcpy()... why?
From: rod at proteancode.com (Roderick Chapman)
Date: Fri, 19 Jul 2019 16:14:01 +0100
In-reply-to: <CA+yPOVhRq4+e6rZCGFTUdHTzDQ5r4kLdUvSLMUgfntnsKyKogw@mail.gmail.com>
References: <2e187c1a-d6d6-3738-df66-1ed684eaea4d@proteancode.com> <8c6794c5-fbbb-0597-1ddc-eec34e682c70@proteancode.com> <CA+yPOVhRq4+e6rZCGFTUdHTzDQ5r4kLdUvSLMUgfntnsKyKogw@mail.gmail.com>

On 19/07/2019 13:13, Virgile Prevosto wrote:
> Generally speaking, WP is quite bad at handling memcpy and other 
> functions of its ilk

OK. In that case, what is the preferred and correct method for 
performing assignment of a whole array in Frama-C?

 Â - Rod


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.gforge.inria.fr/pipermail/frama-c-discuss/attachments/20190719/048c2047/attachment.html>

Follow-Ups:
- [Frama-c-discuss] Warnings for call to memcpy()... why?
  - From: virgile.prevosto at m4x.org (Virgile Prevosto)

References:
- [Frama-c-discuss] Warnings for call to memcpy()... why?
  - From: rod at proteancode.com (Roderick Chapman)
- [Frama-c-discuss] Warnings for call to memcpy()... why?
  - From: virgile.prevosto at m4x.org (Virgile Prevosto)

Prev by Date: [Frama-c-discuss] Frama-C on Windows 10 via WSL
Next by Date: [Frama-c-discuss] Warnings for call to memcpy()... why?
Previous by thread: [Frama-c-discuss] Warnings for call to memcpy()... why?
Next by thread: [Frama-c-discuss] Warnings for call to memcpy()... why?
Index(es):
- Date
- Thread