public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "howarth at nitro dot med.uc.edu" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/51031] build error in libitm  (how to disable trans-mem???)
Date: Thu, 10 Nov 2011 00:38:00 -0000	[thread overview]
Message-ID: <bug-51031-4-EVj7vI59gq@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-51031-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #11 from Jack Howarth <howarth at nitro dot med.uc.edu> 2011-11-10 00:30:08 UTC ---
At r181241, x86_64-apple-darwin11, bootstrap now fails at...


libtool: compile:  /sw/src/fink.build/gcc47-4.7.0-1/darwin_objdir/./gcc/g++
-B/sw/src/fink.build/gcc47-4.7.0-1/darwin_objdir/./gcc/ -nostdinc++ -nostdinc++
-I/sw/src/fink.build/gcc47-4.7.0-1/darwin_objdir/x86_64-apple-darwin11.2.0/libstdc++-v3/include/x86_64-apple-darwin11.2.0
-I/sw/src/fink.build/gcc47-4.7.0-1/darwin_objdir/x86_64-apple-darwin11.2.0/libstdc++-v3/include
-I/sw/src/fink.build/gcc47-4.7.0-1/gcc-4.7-20111109/libstdc++-v3/libsupc++
-I/sw/src/fink.build/gcc47-4.7.0-1/gcc-4.7-20111109/libstdc++-v3/include/backward
-I/sw/src/fink.build/gcc47-4.7.0-1/gcc-4.7-20111109/libstdc++-v3/testsuite/util
-L/sw/src/fink.build/gcc47-4.7.0-1/darwin_objdir/x86_64-apple-darwin11.2.0/libstdc++-v3/src
-L/sw/src/fink.build/gcc47-4.7.0-1/darwin_objdir/x86_64-apple-darwin11.2.0/libstdc++-v3/src/.libs
-B/sw/lib/gcc4.7/x86_64-apple-darwin11.2.0/bin/
-B/sw/lib/gcc4.7/x86_64-apple-darwin11.2.0/lib/ -isystem
/sw/lib/gcc4.7/x86_64-apple-darwin11.2.0/include -isystem
/sw/lib/gcc4.7/x86_64-apple-darwin11.2.0/sys-include -DHAVE_CONFIG_H -I.
-I../../../gcc-4.7-20111109/libitm
-I../../../gcc-4.7-20111109/libitm/config/x86
-I../../../gcc-4.7-20111109/libitm/config/posix
-I../../../gcc-4.7-20111109/libitm/config/generic
-I../../../gcc-4.7-20111109/libitm -std=gnu++0x -funwind-tables -fno-exceptions
-fno-rtti -Wall -pthread -Werror -mavx -fabi-version=4 -g -O2 -MT x86_avx.lo
-MD -MP -MF .deps/x86_avx.Tpo -c
../../../gcc-4.7-20111109/libitm/config/x86/x86_avx.cc  -fno-common -DPIC -o
.libs/x86_avx.o
/var/tmp//ccBoRKx4.s:44:no such instruction: `vmovaps 16(%rsp), %ymm0'
/var/tmp//ccBoRKx4.s:92:no such instruction: `vmovaps 16(%rsp), %ymm0'
/var/tmp//ccBoRKx4.s:140:no such instruction: `vmovaps 16(%rsp), %ymm0'
/var/tmp//ccBoRKx4.s:188:no such instruction: `vmovaps 16(%rsp), %ymm0'
/var/tmp//ccBoRKx4.s:215:no such instruction: `vmovaps %ymm0, 32(%rsp)'
/var/tmp//ccBoRKx4.s:217:no such instruction: `vzeroupper'
/var/tmp//ccBoRKx4.s:263:no such instruction: `vmovaps %ymm0, 32(%rsp)'
/var/tmp//ccBoRKx4.s:265:no such instruction: `vzeroupper'
/var/tmp//ccBoRKx4.s:311:no such instruction: `vmovaps %ymm0, 32(%rsp)'
/var/tmp//ccBoRKx4.s:313:no such instruction: `vzeroupper'
make[2]: *** [x86_avx.lo] Error 1
make[1]: *** [all-recursive] Error 1
make: *** [all] Error 2


  parent reply	other threads:[~2011-11-10  0:31 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-08 14:52 [Bug bootstrap/51031] New: " vincenzo.innocente at cern dot ch
2011-11-08 14:57 ` [Bug bootstrap/51031] " dominiq at lps dot ens.fr
2011-11-09  8:58 ` vincenzo.innocente at cern dot ch
2011-11-09 11:48 ` fxcoudert at gcc dot gnu.org
2011-11-09 12:12 ` redi at gcc dot gnu.org
2011-11-09 12:38 ` torvald at gcc dot gnu.org
2011-11-09 13:43 ` vincenzo.innocente at cern dot ch
2011-11-09 13:55 ` dominiq at lps dot ens.fr
2011-11-09 17:03 ` howarth at nitro dot med.uc.edu
2011-11-09 21:38 ` howarth at nitro dot med.uc.edu
2011-11-09 21:45 ` howarth at nitro dot med.uc.edu
2011-11-10  0:38 ` howarth at nitro dot med.uc.edu [this message]
2011-11-10  1:49 ` kargl at gcc dot gnu.org
2011-11-10  2:28 ` rth at gcc dot gnu.org
2011-11-10  2:29 ` howarth at nitro dot med.uc.edu
2011-11-10 10:01 ` vincenzo.innocente at cern dot ch
2011-11-10 10:11 ` dominiq at lps dot ens.fr
2011-11-10 14:47 ` howarth at nitro dot med.uc.edu

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-51031-4-EVj7vI59gq@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).