[issue40455] GCC 10 compiler warnings

Dong-hee Na added the comment: Thank you Pablo!! -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker ___

[issue40455] GCC 10 compiler warnings

Change by Dong-hee Na : -- versions: +Python 3.10 -Python 3.9 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue40455] GCC 10 compiler warnings

Dong-hee Na added the comment: New changeset 86e322f1412be6c5a6c8fa8e73af68b99c42bb18 by Pablo Galindo in branch 'master': bpo-40455: Fix gcc10+ warning about writing into a section of offset 0 (GH-24384) https://github.com/python/cpython/commit/86e322f1412be6c5a6c8fa8e73af68b99c42bb18

[issue40455] GCC 10 compiler warnings

Change by Pablo Galindo Salgado : -- nosy: +pablogsal nosy_count: 5.0 -> 6.0 pull_requests: +23200 pull_request: https://github.com/python/cpython/pull/24384 ___ Python tracker

[issue40455] GCC 10 compiler warnings

Emmanuel Arias added the comment: Hi, I've on my Debian (testing) the reported warning: In function ‘assemble_lnotab’, inlined from ‘assemble_emit’ at Python/compile.c:5706:25, inlined from ‘assemble’ at Python/compile.c:6048:18: Python/compile.c:5660:19: warning: writing 1 byte into a

[issue40455] GCC 10 compiler warnings

Change by hai shi : -- nosy: +shihai1991 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue40455] GCC 10 compiler warnings

STINNER Victor added the comment: There are still warnings on compile.c: https://buildbot.python.org/all/#/builders/448/builds/130 Python/compile.c:5660:19: warning: writing 1 byte into a region of size 0 [-Wstringop-overflow=] Python/compile.c:5660: warning: writing 1 byte into a region of

[issue40455] GCC 10 compiler warnings

Change by Mark Dickinson : -- nosy: -mark.dickinson ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue40455] GCC 10 compiler warnings

Andy Lester added the comment: For anyone following along, note that the PR above is different than the original suggestion. The PR correctly sets x_size, not leaving it zero. -- ___ Python tracker

[issue40455] GCC 10 compiler warnings

Dong-hee Na added the comment: New changeset b88cd585d36d6285a5aeb0b6fdb70c134062181e by Dong-hee Na in branch 'master': bpo-40455: Remove gcc10 warning about x_digits (#19852) https://github.com/python/cpython/commit/b88cd585d36d6285a5aeb0b6fdb70c134062181e --

[issue40455] GCC 10 compiler warnings

Change by Dong-hee Na : -- keywords: +patch pull_requests: +19169 stage: -> patch review pull_request: https://github.com/python/cpython/pull/19852 ___ Python tracker ___

[issue40455] GCC 10 compiler warnings

Dong-hee Na added the comment: @mark.dickinson @vstinner I'd like to suggest this change. There was no performance impact on my local machine. --- a/Objects/longobject.c +++ b/Objects/longobject.c @@ -2852,7 +2852,8 @@ _PyLong_Frexp(PyLongObject *a, Py_ssize_t *e) { Py_ssize_t a_size,

[issue40455] GCC 10 compiler warnings

Mark Dickinson added the comment: As to _why_ it's a false positive: at that point in the code, assuming 30-bit limbs and an IEEE 754 binary64 "double", we have (using Python notation for floor division) a_size == 1 + (a_bits - 1) // 30 and shift_digits == (a_bits - 55) // 30

[issue40455] GCC 10 compiler warnings

Mark Dickinson added the comment: I'm fairly sure that that's a false positive for `longobject.c`. Do you know of a non-intrusive way to silence the warning? -- ___ Python tracker

[issue40455] GCC 10 compiler warnings

Change by Mark Dickinson : -- nosy: +mark.dickinson ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue40455] GCC 10 compiler warnings

STINNER Victor added the comment: Andy Lester: > Did you add any options to the ./configure call for cpython? What were they? I reported warnings that I saw on a buildbot build. Extract of https://buildbot.python.org/all/#/builders/351/builds/406. configure step: ./configure --prefix

[issue40455] GCC 10 compiler warnings

Andy Lester added the comment: Did you add any options to the ./configure call for cpython? What were they? -- ___ Python tracker ___

[issue40455] GCC 10 compiler warnings

Change by Andy Lester : -- nosy: +petdance ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue40455] GCC 10 compiler warnings

New submission from STINNER Victor : GCC 10.0.1 on PPC64LE Fedora Rawhide LTO 3.x buildbot: https://buildbot.python.org/all/#/builders/351/builds/406 Objects/longobject.c: In function ‘_PyLong_Frexp’: Objects/longobject.c:2928:33: warning: ‘x_digits[0]’ may be used uninitialized in this