- Mar 15, 2019
-
-
Pierre Loic Garoche authored
By default traces are not produced. Requires the option -t to produce them
-
- Mar 14, 2019
-
-
Pierre Loic Garoche authored
- now properly records the scopes - only register requested ones
-
- Mar 13, 2019
-
-
Pierre Loic Garoche authored
-
Pierre Loic Garoche authored
-
- Mar 12, 2019
-
-
Pierre Loic Garoche authored
-
Pierre Loic Garoche authored
-
Pierre Loic Garoche authored
-
- Nov 17, 2018
-
-
Pierre Loic Garoche authored
-
Pierre Loic Garoche authored
-
Pierre Loic Garoche authored
-
Pierre Loic Garoche authored
-
Pierre Loic Garoche authored
-
Pierre Loic Garoche authored
- Nov 16, 2018
-
-
Pierre Loic Garoche authored
-
Pierre Loic Garoche authored
-
Pierre Loic Garoche authored
-
Pierre Loic Garoche authored
-
Pierre Loic Garoche authored
-
Pierre Loic Garoche authored
-
Pierre Loic Garoche authored
-
- Nov 15, 2018
-
-
Pierre Loic Garoche authored
-
Pierre Loic Garoche authored
-
Pierre Loic Garoche authored
-
Pierre Loic Garoche authored
-
Pierre Loic Garoche authored
-
Pierre Loic Garoche authored
- a bug in regressio ntest Simulink/integrator_ext_IC_matrix_test revealed the following (serious issue): when building the list of instruction (in the machine code) the access to variable were hardcoded to LocalVar or StateVAr depending whether the variables was part of the identified memories. Un fortunately the set of memories is only known after iterating through all definitions. A read access to a memory which was scheduled before its update was generating a non compilable C code: the access to the memory x which should be written as mem->x was written as a local access "x". But x was not declared as a local variable: hence gcc compile error. The current commit is pretty involved. It goes through all the code: - LocalVar and StateVar have been merged in Var in machine instructions (rhs ie expressions) - any possible print or access to these shall be given access to the machine (ie its memories) so a lot of functions have been enriched with a machine first argument. Regression tests performed well showing no additional bug introduced. The only Unstable->Broken changes are the DIFF which could not be run at all before.
-
Pierre Loic Garoche authored
-
- Nov 14, 2018
-
-
Pierre Loic Garoche authored
-
- Nov 13, 2018
-
-
Pierre Loic Garoche authored
-
Pierre Loic Garoche authored
-
- Nov 12, 2018
-
-
Pierre Loic Garoche authored
-
- Nov 10, 2018
-
- Nov 08, 2018
-
-
Pierre Loic Garoche authored
Mainly adapting to new cocospec syntax for contracts
-
- Oct 08, 2018
-
-
Pierre Loic Garoche authored
- Adapted the parsing of specification with a cocospec compatible one - The data structure of contracts is now almost cocospec compatible - Lustrec-test has been updated to use the newest syntax
-
- Oct 05, 2018
-
-
Pierre Loic Garoche authored
Adapted the parser/types/constructors for cocospec syntax
-
- Sep 25, 2018
-
-
Pierre Loic Garoche authored
-
Pierre Loic Garoche authored
-
Pierre Loic Garoche authored
-