Re: [boost] [release] 1.75.0 post-beta merges
...failed testing.capture-output ..\..\bin.v2\libs\filesystem\test\operations_unit_test.test\clang-win-10.0.0\release\threading-multi\operations_unit_test.run...
...
This looks like a Clang x86 codegen bug. The compiler returns the `file_status` from `get_status` on the stack and then overwrites it with `push` instructions for some reason.
Not the first x86 clang-cl problem. I'll upgrade from 10.0 to 11.0 to see if it's fixed.
Still not fixed in 11.0.
On 11/27/20 1:13 AM, Peter Dimov via Boost wrote:
...failed testing.capture-output ..\..\bin.v2\libs\filesystem\test\operations_unit_test.test\clang-win-10.0.0\release\threading-multi\operations_unit_test.run...
...
This looks like a Clang x86 codegen bug. The compiler returns the `file_status` from `get_status` on the stack and then overwrites it with `push` instructions for some reason.
Not the first x86 clang-cl problem. I'll upgrade from 10.0 to 11.0 to see if it's fixed.
Still not fixed in 11.0.
Looks like the bug is limited to 32-bit target. Do they actually plan to support 32 bits?
Andrey Semashev wrote:
On 11/27/20 1:13 AM, Peter Dimov via Boost wrote:
...failed testing.capture-output ..\..\bin.v2\libs\filesystem\test\operations_unit_test.test\clang-win-10.0.0\release\threading-multi\operations_unit_test.run...
...
This looks like a Clang x86 codegen bug. The compiler returns the `file_status` from `get_status` on the stack and then overwrites it with `push` instructions for some reason.
Not the first x86 clang-cl problem. I'll upgrade from 10.0 to 11.0 to see if it's fixed.
Still not fixed in 11.0.
Looks like the bug is limited to 32-bit target. Do they actually plan to support 32 bits?
I don't know what "plan to" is supposed to mean; they already support it and have done so for years now. I routinely run Boost tests with it. It's just slightly buggy. :-) (Admittedly I rarely use variant=release, so it might be buggier than I think.)
On 11/27/20 1:42 AM, Peter Dimov via Boost wrote:
Andrey Semashev wrote:
Looks like the bug is limited to 32-bit target. Do they actually plan to support 32 bits?
I don't know what "plan to" is supposed to mean; they already support it and have done so for years now. I routinely run Boost tests with it. It's just slightly buggy. :-)
Yes, I was just under impression that 32-bit target is deprecated or something. Maybe I was just imagining it. Anyway, I don't think I'm going to add any workarounds for this bug. Not that I found any.
participants (2)
-
Andrey Semashev -
Peter Dimov