Johan Euphrosine
Johan Euphrosine
It would be nice if dslx could deduce parametric function params from the type of left-hand, like in: ``` fn foo() -> uN[SZ] { uN[SZ]:42 } #[test] fn foo_test() {...
Currently the many bazel rules relies on implicit output from other rules, ex: - https://google.github.io/xls/bazel_rules_macros/#xls_ir_opt_ir - https://google.github.io/xls/bazel_rules_macros/#xls_ir_verilog all expect their `src` attribute to ends with `.ir` and won't accept a...
The following snippet: ``` import std fn uadd8(a: u8, b: u8) -> u8 { let (_, sum) = std::uadd_with_overflow(a, b); sum } #[test] fn adders_test() { assert_eq(uadd8(u8:1, u8:2), u8:3); }...
It seems that attempting to return an explicit foreign parametric type literal from a parametric func: ``` import apfloat; fn some_apfloat () -> apfloat::APFloat { apfloat::APFloat{ sign: u1:1, bexp: uN[F_EXP_SZ]:2,...
- default on `PDK_ROOT` if set - if not set, enable thru `volare`
Currently open_pdks installs technology file in the current directory layout: ``` /home/proppy/.volare/sky130A/libs.tech/klayout /home/proppy/.volare/sky130A/libs.tech/klayout/drc /home/proppy/.volare/sky130A/libs.tech/klayout/scripts /home/proppy/.volare/sky130A/libs.tech/klayout/tech /home/proppy/.volare/sky130A/libs.tech/klayout/tech/sky130A.lyp /home/proppy/.volare/sky130A/libs.tech/klayout/tech/sky130A.lyt /home/proppy/.volare/sky130A/libs.tech/klayout/lvs /home/proppy/.volare/sky130A/libs.tech/klayout/pymacros /home/proppy/.volare/sky130A/libs.tech/klayout/macros /home/proppy/.volare/sky130A/libs.tech/klayout/ruby /home/proppy/.volare/sky130A/libs.tech/klayout/python /home/proppy/.volare/sky130A/libs.tech/klayout/klayoutrc ``` which is slightly different from the...
Seems like we forgot to define `LINK_TARGETS_D` as part of #351.
per https://www.klayout.de/doc/about/technology_manager.html#:~:text=The%20technology%20folder%20may%20have%20subfolders%20to%20hold%20library%20files%2C%20macros%2C%20DRC%20runsets%2C%20LEF%20files%20and%20other%20pieces%20of%20the%20technology%20package > Except for the default technology, technologies are kept in technology folders in KLayout's application path. They are read from subfolders from the "tech" directories. The technology definition...
I noticed that skywater adds the following to `xschemrc`: https://github.com/RTimothyEdwards/open_pdks/blob/master/sky130/custom/xschem/xschemrc_append Should open_pdks do the same for gf180mcu?
It would be nice if the dependencies on `js-beautify` was optional as it brings quite a few transitive dependencies: ``` ├─┬ [email protected] │ ├─┬ [email protected] │ │ ├── [email protected] │...