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

Clearqfbwjb #78

Closed
wants to merge 3 commits into from
Closed

Clearqfbwjb #78

wants to merge 3 commits into from

Conversation

wjblanke
Copy link
Contributor

No description provided.

@wjblanke
Copy link
Contributor Author

Changed

a shorter way of saying this is just:

qfb fr{}, fr2{}, fr3{};

@wjblanke wjblanke closed this May 12, 2021
@wjblanke wjblanke reopened this May 12, 2021
@wjblanke wjblanke requested a review from arvidn May 12, 2021 20:36
@@ -193,7 +193,7 @@ void qfb_nucomp(qfb_t r, const qfb_t f, const qfb_t g, mpz_t& D, mpz_t& L)

// a = b * c
void nucomp_form(form &a, form &b, form &c, integer &D, integer &L) {
qfb fr, fr2, fr3;
Copy link
Contributor

Choose a reason for hiding this comment

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

actually, it it occurred to me this morning; do we ever want to declare qfb objects that are uninitialized? If not, we should just do this in its constructor and rest assured we won't have this problem again.

@arvidn
Copy link
Contributor

arvidn commented May 13, 2021

I'll test this on raspberry PI

@arvidn
Copy link
Contributor

arvidn commented May 13, 2021

this does not solve the problem. I have a debug build on RPi now though, so I'll investigate

@arvidn
Copy link
Contributor

arvidn commented May 13, 2021

#79

@wjblanke wjblanke closed this May 18, 2021
@emlowe emlowe deleted the clearqfbwjb branch October 4, 2023 14:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants