public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ncahill_alt at yahoo dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libitm/52695] New: libitm/config/x86/cacheline.h: '__m64' does not name a type
Date: Fri, 23 Mar 2012 21:23:00 -0000	[thread overview]
Message-ID: <bug-52695-4@http.gcc.gnu.org/bugzilla/> (raw)

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

             Bug #: 52695
           Summary: libitm/config/x86/cacheline.h: '__m64' does not name a
                    type
    Classification: Unclassified
           Product: gcc
           Version: 4.7.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: libitm
        AssignedTo: unassigned@gcc.gnu.org
        ReportedBy: ncahill_alt@yahoo.com


While building gcc 4.7.0, libitm fails with this error:

In file included from ../../../gcc-4.7.0/libitm/libitm_i.h:85:0,
                 from ../../../gcc-4.7.0/libitm/aatree.cc:28:
../../../gcc-4.7.0/libitm/config/x86/cacheline.h:55:3: error: '__m64' does not
name a type

A possible fix is to add #include <x86intrin.h> 
to cacheline.h, which seems to be the desired intent.

This was built with gcc 4.6.2, from the gcc-4.7.0.tar.bz2 as released on
ftp.gnu.org.  The error occured right at the end, after the bootstrap process
was successful.

Thank you.
Neil.


             reply	other threads:[~2012-03-23 21:19 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-23 21:23 ncahill_alt at yahoo dot com [this message]
2012-03-23 21:30 ` [Bug libitm/52695] " pinskia at gcc dot gnu.org
2012-03-23 22:28 ` ncahill_alt at yahoo dot com
2012-03-23 23:13 ` pinskia at gcc dot gnu.org
2012-03-24 10:33 ` ncahill_alt at yahoo dot com
2012-03-24 13:33 ` jakub at gcc dot gnu.org
2012-03-28  7:18 ` freebsd at nagilum dot org
2014-01-02  7:37 ` dirtyepic at gentoo dot org
2015-01-23 15:02 ` torvald at gcc dot gnu.org
2015-01-23 17:16 ` rth 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-52695-4@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).