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] usage of Frama_C_memcpy
- Subject: [Frama-c-discuss] usage of Frama_C_memcpy
- From: stephane.duprat at atosorigin.com (Stephane DUPRAT)
- Date: Thu, 03 Dec 2009 13:01:04 +0100
- In-reply-to: <FC0686BB6178BC43B9DC035287A11A720DBE768CD3@SI-MBX12.de.bosch.com>
- References: <1259838582.5991.14.camel@valin.toulouse.it.atosorigin.com> <FC0686BB6178BC43B9DC035287A11A720DBE768CD3@SI-MBX12.de.bosch.com>
Boris, This function is used in the file libc.c in the shared directory of frama-c. The share path of frama-c is given by the command "frama-c -v" (for exemple "Share path: /TOOLS/FRAMA-C/install/frama-c-Beryllium-20090902/share/frama-c (may be overridden with FRAMAC_SHARE variable)"). Regards St?phane Hollas Boris (CR/AEY1) a ?crit : > Hello Stephane, > > what is the builtin Frama_C_memcpy function? Is it related to the libc memcpy function? > > Regards, > Boris > > > -- ----------------------------------------------- Stephane DUPRAT Innovation et Bureau m?thode R?gion Midi-Pyr?n?es - Agence de Toulouse 6 Impasse Alice Guy B.P. 43045 31024 - Toulouse Cedex 03 T?l : 05 34 36 32 78 Fax : 05 34 36 31 00 mailto :stephane.duprat at atosorigin.com ======================================================================= Ce message electronique est confidentiel. Il peut contenir des informations protegees par le secret professionnel, le secret de fabrication ou autres regles legales. Si vous recevez ce message par erreur, il vous est interdit de le reproduire ou de le distribuer en tout ou en partie, ou de le divulguer de quelque maniere que ce soit a quelque personne que ce soit. Nous vous prions de bien vouloir en informer Atos Origin, par telephone ou par retour d'e-mail puis de detruire le message et toutes copies de votre systeme informatique. Le contenu de ce message ne reflete pas necessairement ni les opinions d'Atos Origin ni celle des membres de son groupe. Bien que l'emetteur de ce message ait fait tout son possible pour maintenir son systeme informatique sans virus, il ne peut garantir que cette transmission ne comporte aucun virus et il ne pourra etre tenu pour responsable de quelque dommage que ce soit resultant de la transmission d'un virus. ======================================================================= This electronic transmission is confidential. It may contain information that is covered by legal professional privilege, work product immunity or other legal rules. If you have received this transmission in error, you must not copy or distribute this message or any part of it or otherwise disclose its contents to anyone. Please notify Atos Origin Legal Services by telephone or return E-mail, and then delete this transmission and any copies of it from your computer system. The views expressed in this electronic transmission do not necessarily reflect those of Atos Origin SA or any member of its group. Although the sender endeavours to maintain a computer virus free network, the sender does not warrant that this transmission is virus free and will not be liable for any damages resulting from any virus transmitted. =======================================================================
- References:
- [Frama-c-discuss] usage of Frama_C_memcpy
- From: stephane.duprat at atosorigin.com (Stéphane Duprat)
- [Frama-c-discuss] usage of Frama_C_memcpy
- From: Boris.Hollas at de.bosch.com (Hollas Boris (CR/AEY1))
- [Frama-c-discuss] usage of Frama_C_memcpy
- Prev by Date: [Frama-c-discuss] Problem with bitwise xor
- Next by Date: [Frama-c-discuss] Lemma from ACSL doc doesn't verify
- Previous by thread: [Frama-c-discuss] usage of Frama_C_memcpy
- Next by thread: [Frama-c-discuss] usage of Frama_C_memcpy
- Index(es):