Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

DFCxx -> SystemVerilog pipeline parametrization #24

Merged
merged 1 commit into from
Jul 1, 2024

Conversation

Muxianesty
Copy link
Collaborator

Mentioned in #23 .

DFCxx now supports different output paths for different artifacts.
Now an output path for SystemVerilog has to be set explicitly (option --out <PATH>)

@Muxianesty Muxianesty added the enhancement New feature or request label Jun 28, 2024
@Muxianesty Muxianesty requested a review from ssmolov June 28, 2024 21:23
@Muxianesty Muxianesty self-assigned this Jun 28, 2024
Copy link
Collaborator

@ssmolov ssmolov left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

When applying this PR, I receive a segmentation fault upon the following usage of the tool:

build/src/umain hls --config examples/polynomial2/polynomial2.json -l

@Muxianesty
Copy link
Collaborator Author

Muxianesty commented Jul 1, 2024

When applying this PR, I receive a segmentation fault upon the following usage of the tool:

build/src/umain hls --config examples/polynomial2/polynomial2.json -l

I mentioned this in the PR's description: Now an output path for SystemVerilog has to be set explicitly (option --out <PATH>).
I didn't include this in README.md, because this PR is intermediate and README.md will change in another Pull Request with CLI being able to support different output formats.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants