On Wed, Nov 13, 2024 at 3:58 PM Jeffrey Walton <noloader@xxxxxxxxx> wrote:
On Wed, Nov 13, 2024 at 1:33 PM Patrick Dupre via users
<users@xxxxxxxxxxxxxxxxxxxxxxx> wrote:
>
> I am not sure this issue is entirely relevant on this mailing list.
> Maybe you could redirect me.
>
> Which one is the good one?
> Why this behavior?
Some software uses different code depending on the CPU model.
> Can I solve the issue?
The normal process to understand problems like this is to isolate a minimal
section of code where the problem occurs. Sometimes that doesn't work,
e.g., because the real issue is some out-of-bounds overwriitng of the data.
A small example allows you or gsl devs to experiment with compiler options
and use gdb to step thru the code, but at that point you may just be duplicating
work others have already done, so the main value would be as a learning exercise.
I would take the issue to the libgsl folks at
<https://www.gnu.org/software/gsl/>. The help-gsl <help-gsl@xxxxxxx>
users mailing list looks like the right place.
I would not be surprised if they knew the problem based on your description.
Jeff
Same here. You may be asked to provide a stripped down test case (which
can be added to the existing list of tests).
George N. White III
-- _______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue