[issue40223] Add -fwrapv for new icc versions

2020-06-09 Thread Laël Cellier
Laël Cellier added the comment: since ‑fwrapv is the default with ɢᴄᴄ as ‑O2 is used in Cpython build scripts. -- ___ Python tracker <https://bugs.python.org/issue40

[issue40223] Add -fwrapv for new icc versions

2020-06-09 Thread Laël Cellier
Laël Cellier added the comment: No I’m meaning disabling all optimization when using gcc and using ‑ftrapv. This should cause the same problem : a crashing binary… -- ___ Python tracker <https://bugs.python.org/issue40

[issue40223] Add -fwrapv for new icc versions

2020-06-09 Thread Laël Cellier
Laël Cellier added the comment: If -fwrapv isn’t enabled (whereas with gcc this is the default with ‑O2), then it means -ftrapv is enabled. And from the manual page : This option generates traps for signed overflow on addition, subtraction, multiplication operations. Did you checked if the

[issue40923] Thread safety : disable intel’s compiler autopar where it’s being relevant.

2020-06-09 Thread Laël Cellier
Laël Cellier added the comment: I’m talking about the latest icc installed along with Parallel studio xe. -- ___ Python tracker <https://bugs.python.org/issue40

[issue40923] Thread safety : disable intel’s compiler autopar where it’s being relevant.

2020-06-09 Thread Laël Cellier
Laël Cellier added the comment: I’m using parallel studio xe 2020 and I didn’t receive any crash from icc itself. The problem is the resulting binary which can be downloaded here https://filebin.net/4lp4nb61dav9qamo but that can’t be posted on this issue that is crashing. The only thing I

[issue40923] Thread safety : disable intel’s compiler autopar where it’s being relevant.

2020-06-09 Thread Laël Cellier
Laël Cellier added the comment: Unlike gcc, icc can pretty much parallelize everything while detecting cases like the mutexes used by the ɢɪʟ for deciding not to parallelize. The requirement is to use a less conservative approach using -par-threshold97 while using -par-schedule-auto

[issue40923] Thread safety : disable intel’s compiler autopar where it’s being relevant.

2020-06-08 Thread Laël Cellier
Laël Cellier added the comment: It also turns out the problematic binary can’t be posted here because of a ʜᴛᴛᴘ 413 Entity too large error despite the attachment being only 4MB https://filebin.net/4lp4nb61dav9qamo -- ___ Python tracker <ht

[issue40923] Thread safety : disable intel’s compiler autopar where it’s being relevant.

2020-06-08 Thread Laël Cellier
Laël Cellier added the comment: (about the bug tracker I was meaning server‑side error message) -- ___ Python tracker <https://bugs.python.org/issue40

[issue40923] Thread safety : disable intel’s compiler autopar where it’s being relevant.

2020-06-08 Thread Laël Cellier
New submission from Laël Cellier : As the bug tracker constantly crash over a continuation byte error while using latest Edgeʜᴛᴍʟ’s Edge browser the description is posted here : https://pastebin.com/5AU9HuQk -- components: Build, C API, Interpreter Core messages: 371066 nosy: Laël