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/111739] incorrect code with PGO enabled
Date: Mon, 09 Oct 2023 13:34:17 +0000 [thread overview]
Message-ID: <bug-111739-4-LTRUpWgZIQ@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-111739-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111739
--- Comment #2 from Anonymous <iamanonymous.cs at gmail dot com> ---
(In reply to Richard Biener from comment #1)
> Confirmed with r14-4302 and also with the head of the GCC 13 branch.
>
> It helps if you can produce proper ISO C without implicit int and like.
Thank you for confirming the bug. Moving forward, we will ensure that the code
does not rely on implicit integer types.
next prev parent reply other threads:[~2023-10-09 13:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-09 12:50 [Bug tree-optimization/111739] New: " iamanonymous.cs at gmail dot com
2023-10-09 13:17 ` [Bug tree-optimization/111739] " rguenth at gcc dot gnu.org
2023-10-09 13:34 ` iamanonymous.cs at gmail dot com [this message]
2023-10-19 1:37 ` 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-111739-4-LTRUpWgZIQ@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).