You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, in PR #398 we modify gen parameters as follows:
[globals.flopoco]
conf = "frequency=800 ..."
We use this configuration file by running filament with the --gen-config /path/to/conf.toml argument.
This allows us to insert whatever values we want into the [globals] tag for the flopoco.toml gen framework file.
This is very nice in some aspects as it allows us to modify multiple different frameworks at once without worrying about namespace collisions and the like. It has some downsides, however:
We cannot specify parameters at a component-level, meaning all instances of a component will have the same gen framework settings
The setting is global, meaning if for some reason one module was built to work at a specific value (For example if we wanted XLS pipeline depth = some value we can hand optimize with), specifying this file elsewhere would break that behavior.
There is no relationship between the globals variables and the output filament, I.E. maybe we would want pipeline depth to actually affect the latency of the component output?
The configuration is in a separate file that we have to include every time we compile
I remember we discussed before the possibility of maybe using something like #[attribute=] notation or something like this to achieve the same behavior, but this might run into some of the namespacing issues we mentioned before.
The text was updated successfully, but these errors were encountered:
UnsignedByte
changed the title
Adds a way to specify global values used in a configuration (open an issue to discuss the current implementation)
Add a way to specify global values used in the gen framework
Mar 7, 2024
Currently, in PR #398 we modify
gen
parameters as follows:We use this configuration file by running filament with the
--gen-config /path/to/conf.toml
argument.This allows us to insert whatever values we want into the
[globals]
tag for theflopoco.toml
gen framework file.This is very nice in some aspects as it allows us to modify multiple different frameworks at once without worrying about namespace collisions and the like. It has some downsides, however:
I remember we discussed before the possibility of maybe using something like
#[attribute=]
notation or something like this to achieve the same behavior, but this might run into some of the namespacing issues we mentioned before.The text was updated successfully, but these errors were encountered: