From: Uros Bizjak <ubizjak@gmail.com>
To: "H.J. Lu" <hjl.tools@gmail.com>
Cc: gcc-patches@gcc.gnu.org, Richard Guenther <rguenther@suse.de>,
Jakub Jelinek <jakub@redhat.com>,
Mark Mitchell <mark@codesourcery.com>
Subject: Re: PATCH: PR target/46519: Missing vzeroupper
Date: Thu, 30 Dec 2010 12:42:00 -0000 [thread overview]
Message-ID: <AANLkTi=e2ZemY8AaWx6sGOBS_RMiS3=LG9z9pZ8SMbsq@mail.gmail.com> (raw)
In-Reply-To: <AANLkTi=0tNb1FX7XweRCUQBh6OUjNW7f6+vyO0YuYk=z@mail.gmail.com>
On Wed, Dec 29, 2010 at 4:32 PM, H.J. Lu <hjl.tools@gmail.com> wrote:
>> I think that due to these reasons, the patch should be committed to
>> SVN even in this development stage. Even if the algorithm is not
>> optimal, the patch demonstrably produces substantially better code.
>> This feature has no impact on generic code without -mvzeroupper /
>> -mavx switch, and since there are currently very few AVX users,
>> negligible overall impact.
>>
>>> gcc/
>>>
>>> 2010-12-18 H.J. Lu <hongjiu.lu@intel.com>
>>>
>>> PR target/46519
>>> * config/i386/i386.c (block_info_def): Remove referenced, count
>>> and rescanned.
>>> (move_or_delete_vzeroupper_2): Updated.
>>> (move_or_delete_vzeroupper_1): Rewritten to avoid recursive call.
>>> (rescan_move_or_delete_vzeroupper): Removed.
>>> (move_or_delete_vzeroupper): Repeat processing all basic blocks
>>> until no basic block state is changed to used at exit.
>>>
>>> gcc/testsuite/
>>>
>>> 2010-12-18 H.J. Lu <hongjiu.lu@intel.com>
>>>
>>> PR target/46519
>>> * gfortran.dg/pr46519-2.f90: New.
>>>
>>
>> The patch is OK, but please allow a day or two for RMs (CC'd) to
>> eventually comment.
>
> We will investigate LCM for 4.7. In the meantime, here is a small patch
> on top of the current one. If the upper 128bits are never changed in a basic
> block, we can skip it in the later passes. OK for trunk together with the
> current patch?
>
> 2010-12-29 H.J. Lu <hongjiu.lu@intel.com>
>
> * config/i386/i386.c (upper_128bits_state): Update comments.
> (block_info_def): Add unchanged.
> (move_or_delete_vzeroupper_2): Short circuit if upper 128bits
> are unchanged in the block.
>
OK, but please remove now redundant coments in
@@ -60,14 +60,17 @@ along with GCC; see the file COPYING3. If not see
enum upper_128bits_state
{
unknown = 0, /* Unknown. */
- unused, /* Not used or not referenced. */
- used /* Used or referenced. */
+ unused, /* Not used. */
+ used /* Used. */
};
Thanks,
Uros.
next prev parent reply other threads:[~2010-12-30 11:19 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-17 19:45 H.J. Lu
2010-12-18 19:36 ` Uros Bizjak
2010-12-18 20:11 ` H.J. Lu
2010-12-29 11:03 ` Uros Bizjak
2010-12-29 16:23 ` H.J. Lu
2010-12-30 12:42 ` Uros Bizjak [this message]
2011-01-01 1:05 ` Mark Mitchell
2011-01-01 1:38 ` H.J. Lu
2011-01-01 1:39 ` Mark Mitchell
2011-01-01 2:08 ` H.J. Lu
2011-01-01 2:17 ` Mark Mitchell
2011-01-01 16:01 ` H.J. Lu
2011-01-04 1:15 ` Mark Mitchell
2011-01-04 3:59 ` H.J. Lu
2011-01-04 5:54 ` Mark Mitchell
2011-01-04 22:17 ` H.J. Lu
2011-01-04 23:53 ` Mark Mitchell
2011-01-05 0:06 ` H.J. Lu
2011-01-05 0:08 ` Mark Mitchell
2011-01-05 0:09 ` H.J. Lu
2011-01-05 0:24 ` Mark Mitchell
2011-01-05 16:44 ` H.J. Lu
2011-01-05 17:12 ` Jakub Jelinek
2011-01-05 23:01 ` H.J. Lu
2011-01-13 17:19 ` H.J. Lu
2011-01-13 17:25 ` Mark Mitchell
2011-01-13 18:16 ` Richard Henderson
2011-01-13 18:51 ` H.J. Lu
2011-01-14 16:06 ` Richard Henderson
2011-01-14 16:08 ` H.J. Lu
2011-01-16 8:04 ` H.J. Lu
2011-01-24 18:00 ` Richard Henderson
2011-01-24 18:12 ` H.J. Lu
2011-01-13 18:04 ` Richard Henderson
2011-01-13 18:09 ` H.J. Lu
-- strict thread matches above, loose matches on Subject: below --
2010-11-19 21:58 H.J. Lu
2010-11-20 0:24 ` Richard Guenther
2010-11-20 1:48 ` H.J. Lu
2010-11-20 12:11 ` Richard Guenther
2010-11-20 18:20 ` H.J. Lu
2010-11-24 19:48 ` Uros Bizjak
2010-11-24 19:53 ` H.J. Lu
2010-11-24 19:57 ` Uros Bizjak
2010-11-24 21:41 ` H.J. Lu
2010-11-18 7:29 H.J. Lu
2010-11-18 8:34 ` H.J. Lu
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='AANLkTi=e2ZemY8AaWx6sGOBS_RMiS3=LG9z9pZ8SMbsq@mail.gmail.com' \
--to=ubizjak@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=hjl.tools@gmail.com \
--cc=jakub@redhat.com \
--cc=mark@codesourcery.com \
--cc=rguenther@suse.de \
/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).