From: Marc Glisse <marc.glisse@inria.fr>
To: Hanke Zhang <hkzhang455@gmail.com>
Cc: gcc@gcc.gnu.org
Subject: Re: Question about merging if-else blocks
Date: Wed, 27 Sep 2023 06:51:27 +0200 (CEST) [thread overview]
Message-ID: <3bf388e5-0c20-8294-d99f-5f7c8a74607b@inria.fr> (raw)
In-Reply-To: <CAM_DAs8=kgTU3UbH+KtGdYHQzPc4SM=_owW-mHqVvcrzx47rvg@mail.gmail.com>
On Wed, 27 Sep 2023, Hanke Zhang via Gcc wrote:
> Hi, I have recently been working on merging if-else statement blocks,
> and I found a rather bizarre phenomenon that I would like to ask
> about.
> A rough explanation is that for two consecutive if-else blocks, if
> their if statements are exactly the same, they should be merged, like
> the following program:
>
> int a = atoi(argv[1]);
> if (a) {
> printf("if 1");
> } else {
> printf("else 1");
> }
> if (a) {
> printf("if 2");
> } else {
> printf("else 2");
> }
>
> After using the -O3 -flto optimization option, it can be optimized as follows:
>
> int a = atoi(argv[1]);
> if (a) {
> printf("if 1");
> printf("if 2");
> } else {
> printf("else 1");
> printf("else 2");
> }
>
> But `a` here is a local variable. If I declare a as a global variable,
> it cannot be optimized as above. I would like to ask why this is? And
> is there any solution?
If 'a' is a global variable, how do you know 'printf' doesn't modify its
value? (you could know it for printf, but it really depends on the
function that is called)
--
Marc Glisse
next prev parent reply other threads:[~2023-09-27 4:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-27 3:47 Hanke Zhang
2023-09-27 4:51 ` Marc Glisse [this message]
2023-09-27 5:20 ` Hanke Zhang
2023-09-27 7:28 ` Richard Biener
2023-10-01 4:12 ` Hanke Zhang
2023-10-04 7:54 ` Richard Biener
2023-10-04 9:12 ` Florian Weimer
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=3bf388e5-0c20-8294-d99f-5f7c8a74607b@inria.fr \
--to=marc.glisse@inria.fr \
--cc=gcc@gcc.gnu.org \
--cc=hkzhang455@gmail.com \
/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).