Currently, if look at the windows_e2e tests on circle under the write e2e files step, you will see this warning:

Error autodetecting timing type, falling back to weighting by name. Autodetect no matching filename or classname.  If file names are used, double check paths for absolute vs relative.
Example input file: "e2e\\api\\add-many.e2e.1.ts"
Example file from timings: "C:\\Users\\****

FuseSoC supports use flags, but doesn't document which use flags are actually set. This needs to be documented.

Currently we set:

• A target use flag target_TARGETNAME, e.g. target_sim if fusesoc is called with --target=sim.
• A tool use flags tool_TOOLNAME, e.g. tool_verilator if fusesoc is called with --tool=verilator

Support for user-defined use flags is being developed in #26

• { value } as the main resource to render
• { name, onChange } to enable upwards communication
• Derive behavior from props, not from decorator parameters
• { onPush } to bypass filters
• { onPull } to retrieve value from parent
• More general:
  • { [on${action}] } for upwards communication