From: Marco Atzeri <marco.atzeri@gmail.com>
To: cygwin@cygwin.com
Subject: Re: [ANNOUNCEMENT] Updated: openblas-0.3.14-1
Date: Wed, 19 May 2021 12:56:33 +0200 [thread overview]
Message-ID: <07f0d952-50ae-6f77-68e2-d7afe202e189@gmail.com> (raw)
In-Reply-To: <20210519181218.de23e36e1fcec21656f274a6@nifty.ne.jp>
On 19.05.2021 11:12, Takashi Yano via Cygwin wrote:
> On Wed, 31 Mar 2021 21:03:03 +0200
> Marco Atzeri wrote:
>> New releases 0.3.14-1 of
>>
>
> After upgrading libopenblas from 0.3.12-2 to 0.3.14-1,
> octave 5.2.0 crashes on plot command in 64 bit environment.
> In 32 bit cygwin (WoW64), this does not happen. Reverting
> libopenblas to 0.3.12-1 resolve the issue.
>
> octave:1> plot([])
> fatal: caught signal Illegal instruction -- stopping myself...
> Illegal instruction(core dumped)
>
> My environment:
> OS: Windows 10 20H2 (64 bit)
> CPU: Inte Core i7 870 (Lynnfield)
>
> [yano@Express5800-S70 ~]$ cygcheck -c cygwin octave libopenblas
> Cygwin Package Information
> Package Version Status
> cygwin 3.2.0-1 OK
> libopenblas 0.3.14-1 OK
> octave 5.2.0-1 OK
>
> By starting octave-cli in gdb, it stops at vmovaps instruction
> in gemm_(). IIUC, vmovaps is an AVX instruction which is not
> supported by Core i7 870.
>
> In another PC with Core i7-4790 which supports AVX, the issue
> does not occur.
>
Hi Takashi,
maybe is time to build the 0.3.15 ....
https://github.com/xianyi/OpenBLAS/releases
x86_64:
added support for Intel Control-flow Enforcement Technology (CET)
reverted the DOMATCOPY_RT code to the generic C version
fixed a bug in the AVX512 SGEMM kernel introduced in 0.3.14
fixed misapplication of -msse flag to non-SSE cpus in DYNAMIC_ARCH
added support for compilation of the benchmarks on older OSX versions
fixed propagation of the NO_AVX512 option in CMAKE builds
fixed compilation of the AVX512 SGEMM kernel with clang-cl on Windows
fixed compilation of the CTESTs with INTERFACE64=1 (random faults
on OSX)
corrected the Haswell DROT kernel to require AVX2/FMA3 rather than
AVX512
give me some time, openblas is a bit time consuming
Regards
Marco
next prev parent reply other threads:[~2021-05-19 10:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-31 19:03 Marco Atzeri via Cygwin-announce
2021-05-19 9:12 ` Takashi Yano
2021-05-19 10:56 ` Marco Atzeri [this message]
2021-05-19 14:25 ` Takashi Yano
2021-05-19 16:24 ` Marco Atzeri
2021-05-19 17:21 ` Takashi Yano
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=07f0d952-50ae-6f77-68e2-d7afe202e189@gmail.com \
--to=marco.atzeri@gmail.com \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).