All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bernhard Fischer <rep.dot.nop@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] sparc64 v9 VIS toolchain bug with fzeros?
Date: Sun, 16 Sep 2007 23:25:34 +0200	[thread overview]
Message-ID: <20070916212533.GO20058@aon.at> (raw)
In-Reply-To: <20070915222726.GN20058@aon.at>

Hi Blue Swirl,

Configuring gcc with --with-tune=v9 and -mvis in cflags, how can there
be a call to fzeros (a v9a instruction, from the looks)?

Specifically, i see:
/tmp/buildroot_trunk/build_sparc64/staging_dir/usr/bin/sparc64-linux-uclibc-gcc 
-Os -I/tmp/buildroot_trunk/build_sparc64/staging_dir/usr/include
-I/tmp/buildroot_trunk/build_sparc64/staging_dir/include
--sysroot=/tmp/buildroot_trunk/build_sparc64/staging_dir/ -isysroot
/tmp/buildroot_trunk/build_sparc64/staging_dir -mtune=v9 -mvis
-DHAVE_CONFIG_H -I../ncurses -I. -I. -I../include  -D_GNU_SOURCE
-DNDEBUG -O2 -fPIC -c ../ncurses/./tty/lib_mvcur.c -o
../obj_s/lib_mvcur.o
{standard input}: Assembler messages:
{standard input}:12791: Error: Architecture mismatch on "fzeros".
{standard input}:12791:  (Requires v9a|v9b; requested architecture is v9.)
make[2]: *** [../obj_s/lib_mvcur.o] Error 1
make[2]: Leaving directory `/tmp/buildroot_trunk/build_sparc64/ncurses-5.6/ncurses'

Is this a bug in binutils-2.17.50.0.17/gcc-4.2.1 or is my configuration wrong?

  reply	other threads:[~2007-09-16 21:25 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20070915075059.68EC4A6056@busybox.net>
2007-09-15 12:19 ` [Buildroot] svn commit: trunk/uClibc: ldso/include ldso/ldso/sparc libc/string etc Bernhard Fischer
     [not found]   ` <f43fc5580709150607t4e51b73by878a54e35da00750@mail.gmail.com>
2007-09-15 19:21     ` Bernhard Fischer
2007-09-15 19:41       ` Blue Swirl
2007-09-15 22:27         ` Bernhard Fischer
2007-09-16 21:25           ` Bernhard Fischer [this message]
2007-09-17 17:21             ` [Buildroot] sparc64 v9 VIS toolchain bug with fzeros? Blue Swirl

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=20070916212533.GO20058@aon.at \
    --to=rep.dot.nop@gmail.com \
    --cc=buildroot@busybox.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.