[Bug analyzer/104042] Four memcpy/memset analyzer failures on darwin

2024-04-28 Thread cvs-commit at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104042 --- Comment #9 from GCC Commits --- The releases/gcc-11 branch has been updated by Iain D Sandoe : https://gcc.gnu.org/g:ee2f7a02371aba24f6db6231ae862cd2248bf45f commit r11-11393-gee2f7a02371aba24f6db6231ae862cd2248bf45f Author:

[Bug analyzer/104042] Four memcpy/memset analyzer failures on darwin

2024-04-20 Thread cvs-commit at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104042 --- Comment #8 from GCC Commits --- The releases/gcc-12 branch has been updated by Iain D Sandoe : https://gcc.gnu.org/g:c2cb625eb141cacd0bee6c6ce5888d673ac38ca4 commit r12-10361-gc2cb625eb141cacd0bee6c6ce5888d673ac38ca4 Author:

[Bug analyzer/104042] Four memcpy/memset analyzer failures on darwin

2024-04-01 Thread cvs-commit at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104042 --- Comment #7 from GCC Commits --- The releases/gcc-13 branch has been updated by Iain D Sandoe : https://gcc.gnu.org/g:a5bc8abef90874e81783e0fa34db133da71d1133 commit r13-8548-ga5bc8abef90874e81783e0fa34db133da71d1133 Author:

[Bug analyzer/104042] Four memcpy/memset analyzer failures on darwin

2023-11-03 Thread fxcoudert at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104042 Francois-Xavier Coudert changed: What|Removed |Added Build||x86_64-apple-darwin21

[Bug analyzer/104042] Four memcpy/memset analyzer failures on darwin

2023-08-19 Thread fxcoudert at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104042 --- Comment #5 from Francois-Xavier Coudert --- Patch posted for Darwin at https://gcc.gnu.org/pipermail/gcc-patches/2023-August/627923.html

[Bug analyzer/104042] Four memcpy/memset analyzer failures on darwin

2022-01-15 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104042 --- Comment #4 from Andrew Pinski --- So I suspect they will fail if you default the linux compiler to _FORTIFY_SOURCE=2 then too. (I thought there was a configure option to do that or maybe Debian/Ubuntu has patches for it I forget).

[Bug analyzer/104042] Four memcpy/memset analyzer failures on darwin

2022-01-15 Thread iains at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104042 --- Comment #3 from Iain Sandoe --- erm, that is probably _FORTIFY_SOURCE from the command line.

[Bug analyzer/104042] Four memcpy/memset analyzer failures on darwin

2022-01-15 Thread iains at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104042 --- Comment #2 from Iain Sandoe --- FX, You might be able to force Darwin to use the non-checked versions (perhaps by adding -D_USE_FORTIFY_LEVEL=0)

[Bug analyzer/104042] Four memcpy/memset analyzer failures on darwin

2022-01-15 Thread fxcoudert at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104042 Francois-Xavier Coudert changed: What|Removed |Added Status|UNCONFIRMED |NEW Last reconfirmed|