On 2015-09-30 14:06, 'Bill Hart' via mpir-devel wrote:
for the two algorithms in
question there are no "invalid values".
Why do you say that? For the two variables in question, there are
certainly invalid values: changing the default value from 11 to 0 fixes
the problem. So I would say that the 11 is invalid (or maybe it's only
invalid in combination with other values, but I don't think that matters
much).
The bug is in *all likelihood* caused by the tuning program never having been
run for those arches.
I don't think it is realistic to require for a MPIR release to run the
tuning program on all arches.
That's the motivation for my question: I think the *real* bug is that
there exist invalid values in the first place, not that the tuning
program hasn't been run.
--
You received this message because you are subscribed to the Google Groups
"mpir-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/mpir-devel.
For more options, visit https://groups.google.com/d/optout.
