[issue32375] Compilation warnings in getpath.c with gcc on Ubuntu / -D_FORTIFY_SOURCE=2

STINNER Victor added the comment: I just recompiled the master branch of Python twice using these flags: * -D_FORTIFY_SOURCE=2 -Og * -D_FORTIFY_SOURCE=2 -O3 I got a few warnings, the same that I get without FORTIFY SOURCE. Using -D_FORTIFY_SOURCE=2 -O3, I get one warning, but it's no longer

[issue32375] Compilation warnings in getpath.c with gcc on Ubuntu / -D_FORTIFY_SOURCE=2

Serhiy Storchaka added the comment: Warnings are emitted when compile with gcc-5, gcc-6 and gcc-7, but not when compile with gcc-4.8 or gcc-8. Versions: gcc-4.8 (Ubuntu 4.8.5-4ubuntu8) 4.8.5 gcc-5 (Ubuntu 5.5.0-12ubuntu1) 5.5.0 20171010 gcc-6 (Ubuntu

[issue32375] Compilation warnings in getpath.c with gcc on Ubuntu / -D_FORTIFY_SOURCE=2

STINNER Victor added the comment: See bpo-32030 for my huge refactoring work on the Python initialization code. -- ___ Python tracker

[issue32375] Compilation warnings in getpath.c with gcc on Ubuntu / -D_FORTIFY_SOURCE=2

STINNER Victor added the comment: getpath.c uses many buffers of MAXPATHLEN+1 wide characters. Example: wchar_t argv0_path[MAXPATHLEN+1]; These buffers are initialized to zero to make sure that the last character is always a NULL character. To keep the final

[issue32375] Compilation warnings in getpath.c with gcc on Ubuntu / -D_FORTIFY_SOURCE=2

Change by STINNER Victor : -- title: Compilation warnings with gcc -> Compilation warnings in getpath.c with gcc on Ubuntu / -D_FORTIFY_SOURCE=2 ___ Python tracker