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] Support for RISCV

My guess is that you need to know datatypes sizes for a specific arch for proper static analysis of C code.

On 21 January 2017 12:06:14 CET, "Gerlach, Jens" <jens.gerlach at fokus.fraunhofer.de> wrote:
>Hello,
>
>do you mean https://en.wikipedia.org/wiki/RISC-V ?
>
>I don’t understand what this has to do with static analysis of
>C(!)-code.
>
>Regards
>
>Jens
>    
> ----------------------------------------------------------------------
>    
>    Message: 1
>    Date: Fri, 20 Jan 2017 12:33:49 +0100
>    From: Paulo Matos <pmatos at linki.tools>
>    To: frama-c-discuss at lists.gforge.inria.fr
>    Subject: [Frama-c-discuss] Support for RISCV
>    Message-ID: <9732e061-bac9-7205-b3da-9682f67abe87 at linki.tools>
>    Content-Type: text/plain; charset=utf-8
>    
>    Hello,
>    
>    What's the best place to start if I want to add support for RISCV?
>    
>    Is there any documentation on adding a new backend to Frama-C?
>    
> 
>
>_______________________________________________
>Frama-c-discuss mailing list
>Frama-c-discuss at lists.gforge.inria.fr
>http://lists.gforge.inria.fr/mailman/listinfo/frama-c-discuss

-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.gforge.inria.fr/pipermail/frama-c-discuss/attachments/20170121/a1f20c3a/attachment.html>