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] Help with -wp-init-const and static evaluation of constants

  • Subject: [Frama-c-discuss] Help with -wp-init-const and static evaluation of constants
  • From: virgile.prevosto at m4x.org (Virgile Prevosto)
  • Date: Thu, 18 Jul 2019 08:26:16 +0200
  • In-reply-to: <CA+yPOVjhCvkoyLc1y1y+35cPX-e_P=-4pqyG8FQb=cxp9zZS8w@mail.gmail.com>
  • References: <c5309feb-8597-c141-6dd2-48da2b49e048@proteancode.com> <CA+yPOVjhCvkoyLc1y1y+35cPX-e_P=-4pqyG8FQb=cxp9zZS8w@mail.gmail.com>
Le jeu. 18 juil. 2019 à 08:14, Virgile Prevosto <virgile.prevosto at m4x.org>
a écrit :

>
>
> I've also tried to play with the -constfold option of the kernel, but
> apparently it only operates inside function bodies and not in global
> initializers. I'll take that as a feature wish.
>
>
Come to think of it, -constfold is a pretty old option, which dates back to
a time where frama-c treated const merely as a decoration to a type. Now
that it is more aggressive at tracking down writes into a const location,
it would probably make sense to let -constfold expand the value of
variables declared as const.

Best regards,
-- 
E tutto per oggi, a la prossima volta
Virgile
-------------- section suivante --------------
Une pièce jointe HTML a été nettoyée...
URL: <http://lists.gforge.inria.fr/pipermail/frama-c-discuss/attachments/20190718/378022bf/attachment-0001.html>