-
Notifications
You must be signed in to change notification settings - Fork 883
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
Add default cfg_t and debug_module_config_t constructor to libriscv #1526
Conversation
6d33293
to
4c99a5e
Compare
I didn't look at the code, but the rationale checks out. Probably worth pinging this thread after #1522 is merged. |
I'm not sure I understand the removal of @rswarbrick introduced this in #946 to keep track of which config vars had been overridden from their initial values (e.g. via command-line). Do we not need that capability anymore? |
That capability was never used once the My understanding is that the |
4c99a5e
to
537b593
Compare
Argument parsing should be scoped to the code which constucts cfg_t
537b593
to
0232396
Compare
@aswaterman @scottj97 This is ready now. |
Still OK with me; let's wait for @scottj97 |
I don’t care
…On Sun, Dec 10, 2023 at 7:36 PM Andrew Waterman ***@***.***> wrote:
Still OK with me; let's wait for @scottj97 <https://github.com/scottj97>
—
Reply to this email directly, view it on GitHub
<#1526 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAAVCTTUPEPFMCHTJYPNBFLYIZPTVAVCNFSM6AAAAABALZIKR2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNBZGE4TENJVGA>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Adding additional config options to cfg_t has, up to now, required propagating the flag to all code which instantiates cfg_t, including projects which use Spike as a library.
Now, the default constructor for
cfg_t
will construct the default spike parameters.This should be merged after #1522 to avoid merge conflicts.