public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "hiraditya at msn dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/109441] New: missed optimization when all elements of vector are known
Date: Thu, 06 Apr 2023 18:31:37 +0000 [thread overview]
Message-ID: <bug-109441-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109441
Bug ID: 109441
Summary: missed optimization when all elements of vector are
known
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: tree-optimization
Assignee: unassigned at gcc dot gnu.org
Reporter: hiraditya at msn dot com
Target Milestone: ---
Reference: https://godbolt.org/z/af4x6zhz9
When all elements of vector are 0, then the compiler should be able to remove
the loop and just return 0.
Testcase:
#include<vector>
using namespace std;
using T = int;
T v() {
T s;
std::vector<T> v;
v.resize(1000, 0);
for (auto i = 0; i < v.size(); ++i) {
s += v[i];
}
return s;
}
$ g++ -O3 -std=c++17
.LC0:
.string "vector::_M_fill_insert"
v():
push rbx
pxor xmm0, xmm0
mov edx, 1000
xor esi, esi
sub rsp, 48
lea rcx, [rsp+12]
lea rdi, [rsp+16]
mov QWORD PTR [rsp+32], 0
mov DWORD PTR [rsp+12], 0
movaps XMMWORD PTR [rsp+16], xmm0
call std::vector<int, std::allocator<int>
>::_M_fill_insert(__gnu_cxx::__normal_iterator<int*, std::vector<int,
std::allocator<int> > >, unsigned long, int const&)
mov rdx, QWORD PTR [rsp+24]
mov rdi, QWORD PTR [rsp+16]
mov rax, rdx
sub rax, rdi
mov rsi, rax
sar rsi, 2
cmp rdx, rdi
je .L99
test rax, rax
mov ecx, 1
cmovne rcx, rsi
cmp rax, 12
jbe .L107
mov rdx, rcx
pxor xmm0, xmm0
mov rax, rdi
shr rdx, 2
sal rdx, 4
add rdx, rdi
.L101:
movdqu xmm2, XMMWORD PTR [rax]
add rax, 16
paddd xmm0, xmm2
cmp rdx, rax
jne .L101
movdqa xmm1, xmm0
psrldq xmm1, 8
paddd xmm0, xmm1
movdqa xmm1, xmm0
psrldq xmm1, 4
paddd xmm0, xmm1
movd ebx, xmm0
test cl, 3
je .L99
and rcx, -4
mov eax, ecx
.L100:
lea edx, [rax+1]
add ebx, DWORD PTR [rdi+rcx*4]
movsx rdx, edx
cmp rdx, rsi
jnb .L99
add eax, 2
lea rcx, [0+rdx*4]
add ebx, DWORD PTR [rdi+rdx*4]
cdqe
cmp rax, rsi
jnb .L99
add ebx, DWORD PTR [rdi+4+rcx]
.L99:
test rdi, rdi
je .L98
mov rsi, QWORD PTR [rsp+32]
sub rsi, rdi
call operator delete(void*, unsigned long)
.L98:
add rsp, 48
mov eax, ebx
pop rbx
ret
.L107:
xor eax, eax
xor ecx, ecx
jmp .L100
mov rbx, rax
jmp .L105
v() [clone .cold]:
next reply other threads:[~2023-04-06 18:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-06 18:31 hiraditya at msn dot com [this message]
2023-04-06 18:36 ` [Bug tree-optimization/109441] " pinskia at gcc dot gnu.org
2023-04-06 18:40 ` hiraditya at msn dot com
2023-04-11 13:17 ` rguenth at gcc dot gnu.org
2023-05-17 17:23 ` hiraditya at msn dot com
2023-05-18 5:34 ` rguenth at gcc dot gnu.org
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-109441-4@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).