public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "tejohnson at google dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/44578] GCC generates MMX instructions but fails to generate "emms"
Date: Tue, 30 Apr 2013 05:43:00 -0000	[thread overview]
Message-ID: <bug-44578-4-PCYKaYvzG5@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-44578-4@http.gcc.gnu.org/bugzilla/>


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

--- Comment #12 from Teresa Johnson <tejohnson at google dot com> 2013-04-30 05:43:06 UTC ---
On Mon, Apr 29, 2013 at 10:37 AM, ubizjak at gmail dot com
<gcc-bugzilla@gcc.gnu.org> wrote:
>
> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=44578
>
> --- Comment #10 from Uros Bizjak <ubizjak at gmail dot com> 2013-04-29 17:37:03 UTC ---
> (In reply to comment #9)
>> It does fix the issue I had in this test case. But theoretically can't
>> this pattern still generate an MMX reference in some cases? And I see
>> other instances of the same constraint in i386.md - is there a larger
>> issue here and how can we prevent this?
>
> Yes, leaks of MMX registers were quite problematic in the past. A lot of effort
> went into insn patterns to balance register allocator to allow MMX registers
> when necessary, and to avoid them otherwise. It looks that zero_extendsidi
> pattern was skipped in these efforts.

Thanks for the quick fix!

>
> -mno-mmx can be used to prevent MMX regs, but the allocator is quite well tuned
> nowadays, so instantiation of %mmX registers when not strictly needed will be
> considered a bug.

I found that due to the header file structure I cannot use -mno-mmx in
certain cases - i.e. when including the STL <algorithm> header file
and compiling with c++11. Is this a known issue/limitation?

(after adding "#include <algorithm>" to the top of my test.cc test case):

$ /usr/local/google/home/tejohnson/gcc_trunk_1_validate/bld-gcc/install/bin/g++
-O test.cc -g -S -std=c++11 -mno-mmx
In file included from
/usr/local/google/home/tejohnson/gcc_trunk_1_validate/bld-gcc/install/lib/gcc/x86_64-unknown-linux-gnu/4.9.0/include/xmmintrin.h:35:0,
                 from
/usr/local/google/home/tejohnson/gcc_trunk_1_validate/bld-gcc/install/lib/gcc/x86_64-unknown-linux-gnu/4.9.0/include/x86intrin.h:34,
                 from
/usr/local/google/home/tejohnson/gcc_trunk_1_validate/bld-gcc/install/include/c++/4.9.0/bits/opt_random.h:33,
                 from
/usr/local/google/home/tejohnson/gcc_trunk_1_validate/bld-gcc/install/include/c++/4.9.0/random:51,
                 from
/usr/local/google/home/tejohnson/gcc_trunk_1_validate/bld-gcc/install/include/c++/4.9.0/bits/stl_algo.h:65,
                 from
/usr/local/google/home/tejohnson/gcc_trunk_1_validate/bld-gcc/install/include/c++/4.9.0/algorithm:62,
                 from test.cc:6:
/usr/local/google/home/tejohnson/gcc_trunk_1_validate/bld-gcc/install/lib/gcc/x86_64-unknown-linux-gnu/4.9.0/include/mmintrin.h:31:3:
error: #error "MMX instruction set not enabled"
 # error "MMX instruction set not enabled"
   ^

Thanks,
Teresa

>
> --
> Configure bugmail: http://gcc.gnu.org/bugzilla/userprefs.cgi?tab=email
> ------- You are receiving this mail because: -------
> You are on the CC list for the bug.



--
Teresa Johnson | Software Engineer | tejohnson@google.com | 408-460-2413


  parent reply	other threads:[~2013-04-30  5:43 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-44578-4@http.gcc.gnu.org/bugzilla/>
2012-11-15  6:36 ` kl4yfd at gmail dot com
2012-11-15  6:39 ` kl4yfd at gmail dot com
2012-11-15 12:06 ` jakub at gcc dot gnu.org
2012-11-15 17:05 ` kl4yfd at gmail dot com
2013-04-29 16:44 ` tejohnson at google dot com
2013-04-29 17:13 ` ubizjak at gmail dot com
2013-04-29 17:24 ` tejohnson at google dot com
2013-04-29 17:37 ` ubizjak at gmail dot com
2013-04-30  5:38 ` ubizjak at gmail dot com
2013-04-30  5:43 ` tejohnson at google dot com [this message]
2013-04-30  5:53 ` ubizjak at gmail dot com
2013-04-30  6:07 ` ubizjak at gmail dot com
2010-06-18 10:27 [Bug target/44578] New: " stephen dot dolan at havok dot com
2010-06-18 10:46 ` [Bug target/44578] " rguenth at gcc dot gnu dot org
2010-06-19 17:23 ` ubizjak at gmail dot com

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-44578-4-PCYKaYvzG5@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).