ffc team mailing list archive
-
ffc team
-
Mailing list archive
-
Message #01754
Re: [HG FFC] Cleanup in handling of command-line options. Everything is now put
In the next generation SFC, I've split the options into three groups:
- output: verbosity, logging, cache directories, etc for debugging of
the form compiler itself
- code: anything that affects the generated code
- compilation: anything that affects how the code is compiled by jit
This will be useful for the cache signatures, since the output options
won't change the form module signature. Potentially, I can cache
the generated code using just options.code in the signature,
and let instant cache the compiled modules using both
options.code and options.compilation in the signature.
--
Martin
2008/9/4 FFC <ffc@xxxxxxxxxx>:
> One or more new changesets pushed to the primary ffc repository.
> A short summary of the last three changesets is included below.
>
> changeset: 1176:a41ade906d0e0a7d57f2ca99e4ebc2c265872f6d
> tag: tip
> user: Anders Logg <logg@xxxxxxxxx>
> date: Thu Sep 04 14:36:27 2008 +0200
> files: src/bin/ffc src/ffc/common/constants.py src/ffc/compiler/compiler.py src/ffc/compiler/format/ufcformat.py src/ffc/jit/jit.py
> description:
> Cleanup in handling of command-line options. Everything is now put
> in the same dictionary and the "="s are removed.
>
>
> changeset: 1175:89c3fde1506263955a837431d1f100b040be076d
> user: Anders Logg <logg@xxxxxxxxx>
> date: Thu Sep 04 13:38:06 2008 +0200
> files: ChangeLog setup.py
> description:
> Apply patch from Johannes for Windows install
>
>
> changeset: 1174:b7eb035ad49db8e8a4de2e4a7bde5eccc798003d
> user: Johannes Ring <johannr@xxxxxxxxx>
> date: Thu Sep 04 11:22:32 2008 +0200
> files: setup.py
> description:
> Generate batch files for Windows.
>
> ----------------------------------------------------------------------
> For more details, visit http://www.fenics.org/hg/ffc
> _______________________________________________
> FFC-dev mailing list
> FFC-dev@xxxxxxxxxx
> http://www.fenics.org/mailman/listinfo/ffc-dev
>
Follow ups
References