public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/110472] 60% slowdown with fwrapv when using openmp
Date: Thu, 29 Jun 2023 01:58:28 +0000 [thread overview]
Message-ID: <bug-110472-4-BN9zb1dLXd@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-110472-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110472
Andrew Pinski <pinskia at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target| |x86_64-linux-gnu
--- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
I think it is just wrong iv-opt choices.
Works just fine on aarch64-linux-gnu too:
ubuntu@ubuntu:~/src/upstream-gcc-aarch64\# ~/upstream-gcc/bin/gcc t4.c -O2
-fopenmp
ubuntu@ubuntu:~/src/upstream-gcc-aarch64\# ./a.out ;echo
time: 15.191220
ubuntu@ubuntu:~/src/upstream-gcc-aarch64\# ~/upstream-gcc/bin/gcc t4.c -O2
-fopenmp -fwrapv
ubuntu@ubuntu:~/src/upstream-gcc-aarch64\# ./a.out ;echo
time: 18.854280
ubuntu@ubuntu:~/src/upstream-gcc-aarch64\# ./a.out ;echo
time: 16.705876
ubuntu@ubuntu:~/src/upstream-gcc-aarch64\# ~/upstream-gcc/bin/gcc t4.c -O2
-fopenmp
ubuntu@ubuntu:~/src/upstream-gcc-aarch64\# ./a.out ;echo
time: 17.491387
ubuntu@ubuntu:~/src/upstream-gcc-aarch64\# ./a.out ;echo
time: 17.519264
next prev parent reply other threads:[~2023-06-29 1:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-29 1:38 [Bug tree-optimization/110472] New: " ryanpholt at me dot com
2023-06-29 1:58 ` pinskia at gcc dot gnu.org [this message]
2023-06-29 15:13 ` [Bug middle-end/110472] " ryanpholt at me dot com
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-110472-4-BN9zb1dLXd@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).