public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "uros at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/47440] Use LCM for vzeroupper insertion
Date: Sun, 11 Nov 2012 19:17:00 -0000	[thread overview]
Message-ID: <bug-47440-4-A3FVpoTIsA@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-47440-4@http.gcc.gnu.org/bugzilla/>


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47440

--- Comment #7 from uros at gcc dot gnu.org 2012-11-11 19:17:22 UTC ---
Author: uros
Date: Sun Nov 11 19:17:17 2012
New Revision: 193409

URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=193409
Log:
    PR target/47440
    * config/i386/i386.c (check_avx256_stores): Remove.
    (ix86_check_avx256_register): New.
    (ix86_avx_u128_mode_needed): Use ix86_check_avx256_register.
    Check the whole RTX for 256bit registers using for_each_rtx.
    (ix86_check_avx_stores): New.
    (ix86_avx_u128_mode_after): Change mode of CALL RTX to AVX_U128_CLEAN
    if there are no 256bit registers used in the function return register.
    (ix86_avx_u128_mode_entry): Use ix86_check_avx256_register.
    (ix86_avx_u128_mode_exit): Ditto.


Modified:
    trunk/gcc/ChangeLog
    trunk/gcc/config/i386/i386.c


  parent reply	other threads:[~2012-11-11 19:17 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-24 17:42 [Bug target/47440] New: Use LCM for vzeroupper optimization hjl.tools at gmail dot com
2011-05-19  8:56 ` [Bug target/47440] Use LCM for vzeroupper insertion ubizjak at gmail dot com
2012-03-22  9:24 ` rguenth at gcc dot gnu.org
2012-07-02 14:07 ` rguenth at gcc dot gnu.org
2012-08-22 15:26 ` vbyakovl23 at gmail dot com
2012-08-23 19:16 ` vbyakovl23 at gmail dot com
2012-11-06 18:04 ` ubizjak at gmail dot com
2012-11-06 18:05 ` ubizjak at gmail dot com
2012-11-11 19:17 ` uros at gcc dot gnu.org [this message]
2012-11-14 16:48 ` uros 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-47440-4-A3FVpoTIsA@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).