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] Frama-c with Freescale (Motorola) HCS12 micro controller

  • Subject: [Frama-c-discuss] Frama-c with Freescale (Motorola) HCS12 micro controller
  • From: pascal.cuoq at gmail.com (Pascal Cuoq)
  • Date: Fri, 28 May 2010 14:13:07 +0200
  • In-reply-to: <1275047417.2159.0.camel@iti27>
  • References: <4BFF7708.1090300@tke.fi> <1275047417.2159.0.camel@iti27>
> Frama-C [...] is not specific to a certain
> microcontroller.

More precisely, Frama-C is specific to several architecture/compilation
platforms (a partial list can be obtained with "frama-c -machdep help").
Do not delude yourself into thinking that it is possible
to verify C code without hypotheses on the compilation platform.
Even if we assumed
only the minimal ranges for char, short, and int guaranteed
by the standard, the presence of sizeof(...) in the analyzed code
would bias any analysis sophisticated enough to make a difference
between 2 and 4.

As an extreme example,
switch(e)
{
  case sizeof(int): f();
  case sizeof(long): g();
  default: h();
}

is a *syntactically* correct C program iff sizeof(int) != sizeof(long).

Pascal