public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jankowski938 at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/108740] two identical functions but the code generated differs due to volatile argument
Date: Thu, 09 Feb 2023 21:19:33 +0000 [thread overview]
Message-ID: <bug-108740-4-pScoqtbBan@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-108740-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108740
--- Comment #5 from Piotr <jankowski938 at gmail dot com> ---
(In reply to Andrew Pinski from comment #4)
> (In reply to Piotr from comment #3)
> > (In reply to Richard Biener from comment #2)
> > > Hmm, ICF + re-inlining makes it ignore some of the pointless volatile dance?
> >
> > why the code is different abstracting form the sense of the assignment?
>
> It is the volatileness of the argument. which by the way for C++20 is
> deprecated ...
It does not answer my question. Identical functions - different generated code.
Both have volatile arguments.
prev parent reply other threads:[~2023-02-09 21:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-09 11:17 [Bug c/108740] New: two identical functions but the code generated differs. Why? jankowski938 at gmail dot com
2023-02-09 11:29 ` [Bug c/108740] " jankowski938 at gmail dot com
2023-02-09 14:07 ` [Bug ipa/108740] " rguenth at gcc dot gnu.org
2023-02-09 16:18 ` jankowski938 at gmail dot com
2023-02-09 18:06 ` pinskia at gcc dot gnu.org
2023-02-09 21:19 ` jankowski938 at gmail dot com [this message]
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-108740-4-pScoqtbBan@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).