[Bug 273219] math/openblas: update to 0.3.24

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=273219

--- Comment #28 from Eijiro Shibusawa <phd_kimberlite@yahoo.co.jp> ---
Hi,

I carried out several investigation, so I'm interested in
1) reproduce method of octave issue (both CLANG and GCC build case);
2) check method of numerical correctness of scipy (built with GCC + OPENMP).
Could someone let me know about the above, please?

I think that the issue produces multiple problems
i) build error;
ii) (doubt of) numerical correctness issue.
I tried investigations involve some different build conditions.
[OpenBLAS 0.3.23 (CLANG + SET OPENMP)]
* math/openblas -> OK (poudriere, their own regression test)
* math/octave -> OK (poudriere)
* science/py-scipy -> OK (poudriere)
* lang/julia -> OK (poudriere)
[OpenBLAS 0.3.24 (CLANG + SET OPENMP)]
* math/openblas -> OK (poudriere, their own regression test)
* math/octave -> OK (poudriere) <---- ???
* science/py-scipy -> NG (poudriere-runaway)
* lang/julia -> NG (poudriere-runaway)
[OpenBLAS 0.3.24 (GCC + SET OPENMP)]
* math/openblas -> OK (poudriere, their own regression test)
* math/octave -> OK (poudriere)
* science/py-scipy -> OK (poudriere)
* lang/julia -> OK (poudriere)
[OpenBLAS 0.3.24 (CLANG + UNSET OPENMP)]
* math/openblas -> OK (poudriere, their own regression test)
* math/octave -> OK (poudriere)
* science/py-scipy -> OK (poudriere)
* lang/julia -> OK (poudriere)

I think that
a) it seems passed OpenBLAS's regression test in all case; 
b) it is strange that building octave always succeeds;
c) building scipy and julia seems same build-runaway problem;
d) the problem seems not reproduced under GCC + OpenMP or CLANG + UNSET OpenMP;
e) the issue seems en-bug since v0.2.24.

The CPU of my box is the following.
===
CPU: Intel(R) Core(TM) i7-10700 CPU @ 2.90GHz (2900.00-MHz K8-class CPU)
  Origin="GenuineIntel"  Id=0xa0655  Family=0x6  Model=0xa5  Stepping=5
 
Features=0xbfebfbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE>
 
Features2=0x7ffafbff<SSE3,PCLMULQDQ,DTES64,MON,DS_CPL,VMX,SMX,EST,TM2,SSSE3,SDBG,FMA,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,TSCDLT,AESNI,XSAVE,OSXSAVE,AVX,F16C,RDRAND>
  AMD Features=0x2c100800<SYSCALL,NX,Page1GB,RDTSCP,LM>
  AMD Features2=0x121<LAHF,ABM,Prefetch>
  Structured Extended
Features=0x29c67af<FSGSBASE,TSCADJ,SGX,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,NFPUSG,MPX,RDSEED,ADX,SMAP,CLFLUSHOPT,PROCTRACE>
  Structured Extended Features2=0x40000018<PKU,OSPKE,SGXLC>
  Structured Extended
Features3=0xbc000400<MD_CLEAR,IBPB,STIBP,L1DFL,ARCH_CAP,SSBD>
  XSAVE Features=0xf<XSAVEOPT,XSAVEC,XINUSE,XSAVES>
  IA32_ARCH_CAPS=0x2b<RDCL_NO,IBRS_ALL,SKIP_L1DFL_VME,MDS_NO>
  VT-x: PAT,HLT,MTF,PAUSE,EPT,UG,VPID,VID,PostIntr
  TSC: P-state invariant, performance statistics
===

I'm sorry for delayed reply.
If I obtain a solution to this problem I'll ask you an exp-run.

Thanks in advance!

-- 
You are receiving this mail because:
You are the assignee for the bug.