- Jul 06, 2010
-
-
Pascal Raymond authored
-
Pascal Raymond authored
-
- Jul 02, 2010
-
-
Pascal Raymond authored
-
Erwan Jahier authored
-
Erwan Jahier authored
Add a -tlex option to debug the lexer. Also, rename the rules in parser.mly now that their appear in the manual. This renaming work is in progress though.
-
Erwan Jahier authored
-
Erwan Jahier authored
-
Pascal Raymond authored
-
Erwan Jahier authored
-
- May 21, 2010
-
-
Erwan Jahier authored
-
- May 05, 2010
-
-
Erwan Jahier authored
Add a -tlex option to debug the lexer. Also, rename the rules in parser.mly now that their appear in the manual. This renaming work is in progress though.
-
Erwan Jahier authored
-
- Apr 14, 2010
-
-
Erwan Jahier authored
-
- Apr 13, 2010
-
-
Erwan Jahier authored
-
- Apr 09, 2010
-
-
Erwan Jahier authored
This is useful to be able to compile V4 program that uses include.
-
- Apr 08, 2010
-
-
Erwan Jahier authored
Fix a performance bug that was occuring with programs having a lot of variables and that were using constant.
-
Erwan Jahier authored
-
- Jan 22, 2010
-
-
Erwan Jahier authored
cf test/should_work/NONREG/fresh_name.lus where the local variable _n1e1_1 was defined twice ! The fix contist the following idea : prefix fresh var name by "_", except if at least one user ident begins by "_". In that case, we try to prefix them by "_1", and then "_2", and so on. We take the first possible one. nb : this won't work if the user defined idents from "_1" to "_1073741823" (on 32-bits machine), but I bet that this compiler would die before anyway...
-
Erwan Jahier authored
-
Erwan Jahier authored
-
- Jan 20, 2010
-
-
Erwan Jahier authored
E.g., when creating a fresh var using the name of "L1", I was creating a var names "_L11", and then "_L12", and so on. But if a var is named "L11", "_L111" is created. If if "L1" is used to generate 11 frash vart names, the name "_L111" clashes !!! The fix contist in adding an underscore before : "L1" produces "_L1_1", "_L1_2", ..., and "_L1_11". nb : the naming scheme is still wrong for other reasons... Next fix.
-
Erwan Jahier authored
-
Erwan Jahier authored
-
Erwan Jahier authored
-
Erwan Jahier authored
-
Erwan Jahier authored
-
Erwan Jahier authored
-
- Jan 13, 2010
-
-
Erwan Jahier authored
-
- May 26, 2009
-
-
Erwan Jahier authored
-
Erwan Jahier authored
message if the constant is abstract ("an integer is expected whereas an int is provided" was not a great message...).
-
Erwan Jahier authored
maintaining (ugly and error-prone) hash tables. That change revealed an untriggered bug in EvalClock.check_args: it was wrong to add in subst the substitutions made of the parameters and the arguments (it is enough to unify the clocks of the pars and of the args). For instance, consider the node (in should_work/clock/clock.lus) node clock5(x : bool; y: bool when x; z: bool when y) and the call z2 = clock5(a, b when a, c when e); I was adding y/b in the subst, which was wrong. Other minor changes: - move const_to_val_eff from Eff to UnifyClock. - GetEff.translate_val_exp now returns a substitution, in order to be able to unify clock vars and propagate the resulting substitution.
-
- Mar 12, 2009
-
-
Erwan Jahier authored
not expanded.
-
- Mar 11, 2009
-
-
Erwan Jahier authored
info is attached to all val_exp. Moreover, this allow to perfrom all the type checking in EvalType.f, instead of doin part of it in GetEff.translate_val_exp.
-
Erwan Jahier authored
-
Erwan Jahier authored
expanser to expand the mentioned node.
-
Erwan Jahier authored
maintaining (ugly and error-prone) hash tables.
-
- Mar 09, 2009
-
-
Erwan Jahier authored
constants that are not on the base clock, add the suitable "when" statement if it was not present in the source code (the lic (and the ec/lv4) backend does not perform such kind of clock inference for constants.
-
- Mar 04, 2009
-
-
Erwan Jahier authored
instead of silently generate (syntactically) wrong lustre v4 (or ec).
-
Erwan Jahier authored
(versus raising an internal error...).
-
Erwan Jahier authored
-