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] There may be a problem with the Program Dependence Graph
- Subject: [Frama-c-discuss] There may be a problem with the Program Dependence Graph
- From: jcdemay at rennes.supelec.fr (Jonathan-Christofer Demay)
- Date: Sun, 06 Mar 2011 15:07:34 +0000
- In-reply-to: <1298391125.18524.89.camel@residence>
- References: <1298391125.18524.89.camel@residence>
> Well, 'tmp' is syntactically declared after those function calls, > but because they are in a loop, it can also be considered *before* > the next iteration of loop... So those dependencies are not > 'impossible'. Indeed, I've just never encountered this before because not some many people declare variables in a middle of a loop and up until Carbon, tmp variables were added by frama-c at the begigging of the block. Well, another extra step during preprocessing I guess, moving variables declarations at the beginning of the block. Anyway, thanks for pointing that out :)
- Prev by Date: [Frama-c-discuss] A question on Frama-C input/output analysis
- Next by Date: [Frama-c-discuss] embedded loops
- Previous by thread: [Frama-c-discuss] A question on Frama-C input/output analysis
- Next by thread: [Frama-c-discuss] embedded loops
- Index(es):