-
Notifications
You must be signed in to change notification settings - Fork 389
[Arcilator] Move pipeline into separate library. #9213
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
Conversation
|
Hi. I'd be interested in using arcilator in a more modular fashion. Are you open to moving some of its pieces out of the binary into a library? Happy to re-arrange this if you think this should be organized differently. |
|
Hi @SimonEbner, factoring it into individual pipelines is a very nice idea! Can you put the pipeline implementation in Thanks! |
a7cbe2b to
253025a
Compare
|
Thanks! Updated accordingly. |
c2dac20 to
171315e
Compare
maerhart
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Thanks!
|
Thanks both. Updated and also fixed/updated the logic around |
280c6b4 to
c6f95bb
Compare
Allow re-use of the arcilator library. Split up the large pipeline into finer grained stages and move into its own library. populateHwModuleToArcPipeline is split into: - arcPreprocessingPipeline - arcConversionPipeline - arcOptimizationPipeline - arcStateLoweringPipeline and - arcStateAllocationPipeline
c6f95bb to
5c5b075
Compare
Allow re-use of the arcilator library. Split up the large pipeline into finer grained stages and move into its own library.
populateHwModuleToArcPipeline is split into:
Flags to customize passes are moved from the binary into the corresponding pipeline options.