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

  • Subject: [Frama-c-discuss] Support for RISCV
  • From: boris at yakobowski.org (Boris Yakobowski)
  • Date: Mon, 23 Jan 2017 11:08:09 +0100
  • In-reply-to: <9732e061-bac9-7205-b3da-9682f67abe87@linki.tools>
  • References: <9732e061-bac9-7205-b3da-9682f67abe87@linki.tools>
Hi,

As noticed by the other persons who replied, multiple things may be
required for a new backend. The simplest configuration option is the notion
of "machep" in Frama-C, which is documented in the user manual (section
5.3). If the currently available ones do not fit your hardware, it is
rather easy to write a new one, and to load it dynamically. Otherwise, if
your need more advanced things such as compiler builtins, you will probably
need to write a bit of OCaml code, or at the very least some ACSL
specifications. Do you have specific needs in mind?

HTH,

On Fri, Jan 20, 2017 at 12:33 PM, Paulo Matos <pmatos at linki.tools> wrote:

> 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?
>
> Kind regards,
> --
> Paulo Matos
> _______________________________________________
> Frama-c-discuss mailing list
> Frama-c-discuss at lists.gforge.inria.fr
> http://lists.gforge.inria.fr/mailman/listinfo/frama-c-discuss




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