[Bug libc/29141] _FORTIFY_SOURCE=3 fail for gcc 12/glibc 2.35

2022-05-16 Thread cvs-commit at gcc dot gnu.org via Elfutils-devel
https://sourceware.org/bugzilla/show_bug.cgi?id=29141

--- Comment #7 from cvs-commit at gcc dot gnu.org  ---
The master branch has been updated by Siddhesh Poyarekar
:

https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=61a87530108ec9181e1b18a9b727ec3cc3ba7532

commit 61a87530108ec9181e1b18a9b727ec3cc3ba7532
Author: Siddhesh Poyarekar 
Date:   Fri May 13 10:01:47 2022 +0530

fortify: Ensure that __glibc_fortify condition is a constant [BZ #29141]

The fix c8ee1c85 introduced a -1 check for object size without also
checking that object size is a constant.  Because of this, the tree
optimizer passes in gcc fail to fold away one of the branches in
__glibc_fortify and trips on a spurious Wstringop-overflow.  The warning
itself is incorrect and the branch does go away eventually in DCE in the
rtl passes in gcc, but the constant check is a helpful hint to simplify
code early, so add it in.

Resolves: BZ #29141
Signed-off-by: Siddhesh Poyarekar 

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Bug libc/29141] _FORTIFY_SOURCE=3 fail for gcc 12/glibc 2.35

2022-05-16 Thread cvs-commit at gcc dot gnu.org via Elfutils-devel
https://sourceware.org/bugzilla/show_bug.cgi?id=29141

--- Comment #9 from cvs-commit at gcc dot gnu.org  ---
The release/2.35/master branch has been updated by Siddhesh Poyarekar
:

https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=58947e1fa593cff7b5513d5e8e0c81b0131984b4

commit 58947e1fa593cff7b5513d5e8e0c81b0131984b4
Author: Siddhesh Poyarekar 
Date:   Fri May 13 10:01:47 2022 +0530

fortify: Ensure that __glibc_fortify condition is a constant [BZ #29141]

The fix c8ee1c85 introduced a -1 check for object size without also
checking that object size is a constant.  Because of this, the tree
optimizer passes in gcc fail to fold away one of the branches in
__glibc_fortify and trips on a spurious Wstringop-overflow.  The warning
itself is incorrect and the branch does go away eventually in DCE in the
rtl passes in gcc, but the constant check is a helpful hint to simplify
code early, so add it in.

Resolves: BZ #29141
Signed-off-by: Siddhesh Poyarekar 

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Bug libc/29141] _FORTIFY_SOURCE=3 fail for gcc 12/glibc 2.35

2022-05-16 Thread cvs-commit at gcc dot gnu.org via Elfutils-devel
https://sourceware.org/bugzilla/show_bug.cgi?id=29141

--- Comment #10 from cvs-commit at gcc dot gnu.org  ---
The release/2.34/master branch has been updated by Siddhesh Poyarekar
:

https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=b72bbba23687ed67887d1d18c51cce5cc9c575ca

commit b72bbba23687ed67887d1d18c51cce5cc9c575ca
Author: Siddhesh Poyarekar 
Date:   Fri May 13 10:01:47 2022 +0530

fortify: Ensure that __glibc_fortify condition is a constant [BZ #29141]

The fix c8ee1c85 introduced a -1 check for object size without also
checking that object size is a constant.  Because of this, the tree
optimizer passes in gcc fail to fold away one of the branches in
__glibc_fortify and trips on a spurious Wstringop-overflow.  The warning
itself is incorrect and the branch does go away eventually in DCE in the
rtl passes in gcc, but the constant check is a helpful hint to simplify
code early, so add it in.

Resolves: BZ #29141
Signed-off-by: Siddhesh Poyarekar 
(cherry picked from commit 61a87530108ec9181e1b18a9b727ec3cc3ba7532)

-- 
You are receiving this mail because:
You are on the CC list for the bug.