https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101746

--- Comment #3 from Aldy Hernandez <aldyh at gcc dot gnu.org> ---
(In reply to Christophe Lyon from comment #1)
> In addition on arm:
> 
> 
> FAIL: g++.dg/warn/Wstringop-overflow-4.C  -std=gnu++98 (test for excess
> errors)
> Excess errors:
> /gcc/testsuite/g++.dg/warn/Wstringop-overflow-4.C:148:3: warning: 'void*
> __builtin_memcpy(void*, const void*, unsigned int)' writing 2 bytes into a
> region of size 0 overflows the destination [-Wstringop-overflow=]
> 
> FAIL: g++.dg/warn/Wstringop-overflow-4.C  -std=gnu++14 (test for excess
> errors)
> Excess errors:
> /gcc/testsuite/g++.dg/warn/Wstringop-overflow-4.C:148:3: warning: 'void*
> __builtin_memcpy(void*, const void*, unsigned int)' writing 2 bytes into a
> region of size 0 [-Wstringop-overflow=]
> /gcc/testsuite/g++.dg/warn/Wstringop-overflow-4.C:149:3: warning: 'void*
> __builtin_memcpy(void*, const void*, unsigned int)' writing 3 bytes into a
> region of size 2 [-Wstringop-overflow=]
> 
> FAIL: g++.dg/warn/Wstringop-overflow-4.C  -std=gnu++17 (test for excess
> errors)
> Excess errors:
> /gcc/testsuite/g++.dg/warn/Wstringop-overflow-4.C:148:3: warning: 'void*
> __builtin_memcpy(void*, const void*, unsigned int)' writing 2 bytes into a
> region of size 0 [-Wstringop-overflow=]
> /gcc/testsuite/g++.dg/warn/Wstringop-overflow-4.C:149:3: warning: 'void*
> __builtin_memcpy(void*, const void*, unsigned int)' writing 3 bytes into a
> region of size 2 [-Wstringop-overflow=]
> 
> FAIL: g++.dg/warn/Wstringop-overflow-4.C  -std=gnu++2a (test for excess
> errors)
> Excess errors:
> /gcc/testsuite/g++.dg/warn/Wstringop-overflow-4.C:148:3: warning: 'void*
> __builtin_memcpy(void*, const void*, unsigned int)' writing 2 bytes into a
> region of size 0 [-Wstringop-overflow=]
> /gcc/testsuite/g++.dg/warn/Wstringop-overflow-4.C:149:3: warning: 'void*
> __builtin_memcpy(void*, const void*, unsigned int)' writing 3 bytes into a
> region of size 2 [-Wstringop-overflow=]

There is already PR101688 for this.

Basically, I think all the issues reported here have corresponding PRs opened.

Reply via email to