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] Unknows Pragma
- Subject: [Frama-c-discuss] Unknows Pragma
- From: pascal.cuoq at gmail.com (Pascal Cuoq)
- Date: Fri, 28 May 2010 14:52:50 +0200
- In-reply-to: <AANLkTinL1AJ0k0C_7D6wqlIEe3uBWvLTy5IxzKzc7lIU@mail.gmail.com>
- References: <4BFF8109.email@example.com> <AANLkTinL1AJ0k0C_7D6wqlIEe3uBWvLTy5IxzKzc7lIU@mail.gmail.com>
> Use the option: > > -cpp-command "gcc -C -E -I. - < %1 ?| grep -v pragma\ LINK_INFO > %2" > > in addition to what you were already doing. Actually this is not perfect, since it will mess up the localization (when you respect the rules for pre-processing, most interactions with Frama-C are localized with respect to the original source code). It would be better to replace the "#pragma LINK_INFO ..." lines with empty lines rather than suppress them. I think a 3-line Perl script could do that, but I didn't reach 2010 without learning Perl to start learning it now. Any taker for this most interesting sub-problem? Pascal PS: while you're at it, write a script that accepts the script inputfile -o outputfile syntax, because that's the only syntax recognized for -cpp-command in the distributed binary versions of Frama-C.