public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "iamanonymous.cs at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/111738] incorrect code when PGO is enabled
Date: Tue, 10 Oct 2023 01:50:54 +0000 [thread overview]
Message-ID: <bug-111738-4-rqk7BDiTGo@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-111738-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111738
--- Comment #3 from Anonymous <iamanonymous.cs at gmail dot com> ---
(In reply to Richard Biener from comment #1)
> I can't reproduce. Your git version is quite old, it translates to
> r14-2634-g85da0b40538fb0 for me. It doesn't reproduce with r14-2282 either
> though.
>
> Current is r14-4486-g873586ebc565b6
Hi, Richard. According to your suggestion, we have updated our gcc to the
latest trunk as:
$ gcc -v
Using built-in specs.
COLLECT_GCC=/root/gcc_set/202310092007/bin/gcc
COLLECT_LTO_WRAPPER=/root/gcc_set/202310092007/libexec/gcc/x86_64-pc-linux-gnu/14.0.0/lto-wrapper
Target: x86_64-pc-linux-gnu
Configured with: ../gcc/configure --prefix=/root/gcc_set/202310092007
--with-gmp=/root/build_essential --with-mpfr=/root/build_essential
--with-mpc=/root/build_essential --enable-languages=c,c++ --disable-multilib
Thread model: posix
Supported LTO compression algorithms: zlib
gcc version 14.0.0 20231009 (experimental) (GCC)
git version: dee55cf59ceea989f47e7605205c6644b27a1f78
Then, we compiled the same test program with/without PGO enabled and found that
the results are inconsistent as:
$ gcc -O3 -w -fprofile-generate=profile a.c -o a.out
$ ./a.out
4
$ gcc -O3 -w -fprofile-use=profile -Wno-missing-profile -fprofile-correction
a.c -o a.out
$ ./a.out
32765
next prev parent reply other threads:[~2023-10-10 1:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-09 12:35 [Bug tree-optimization/111738] New: " iamanonymous.cs at gmail dot com
2023-10-09 13:14 ` [Bug tree-optimization/111738] " rguenth at gcc dot gnu.org
2023-10-09 13:38 ` iamanonymous.cs at gmail dot com
2023-10-10 1:50 ` iamanonymous.cs at gmail dot com [this message]
2023-10-19 1:26 ` pinskia 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-111738-4-rqk7BDiTGo@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).