From: "Andrew Pinski" <pinskia@gmail.com>
To: "GCC List" <gcc@gcc.gnu.org>
Subject: [Tuples] Creating a GIMPLE_MODIFY_STMT unnecessary for gimplify_omp_for
Date: Thu, 19 Jun 2008 21:26:00 -0000 [thread overview]
Message-ID: <de8d50360806191426h35523e11g6f0fe68fc6bfce49@mail.gmail.com> (raw)
Hi,
When I was comparing the tuples branch to the trunk, I noticed that
inside gimplify_omp_for, we call build_gimple_modify_stmt and then
fall through to GIMPLE_MODIFY_STMT but really we don't need it. I
have not tested removing it but I thought I would send out what I
found while reviewing gimplify.c.
Thanks,
Andrew Pinski
reply other threads:[~2008-06-19 21:26 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=de8d50360806191426h35523e11g6f0fe68fc6bfce49@mail.gmail.com \
--to=pinskia@gmail.com \
--cc=gcc@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).