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] [Jessie] pset_disjoint
- Subject: [Frama-c-discuss] [Jessie] pset_disjoint
- From: Boris.Hollas at de.bosch.com (Hollas Boris (CR/AEY1))
- Date: Tue, 9 Jun 2009 17:13:17 +0200
Hello, I'm unable to verify the code below. It seems that Jessie requires that p and q are pointers to distinct memory locations. However, this is not required by Copy. Is this a bug? Regards, Boris /*@ requires \valid(p) && \valid(q); */ void Copy(int *p, int *q) { *q = *p; } void foo() { int a[] = {1,2,3}; Copy(&a[1], &a[1]); }
- Follow-Ups:
- [Frama-c-discuss] [Jessie] pset_disjoint
- From: virgile.prevosto at cea.fr (Virgile Prevosto)
- [Frama-c-discuss] [Jessie] pset_disjoint
- Prev by Date: [Frama-c-discuss] Inductive definition of reachability inarray-implemented list.
- Next by Date: [Frama-c-discuss] [Jessie] pset_disjoint
- Previous by thread: [Frama-c-discuss] Array elements passed as reference
- Next by thread: [Frama-c-discuss] [Jessie] pset_disjoint
- Index(es):