All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bernhard Fischer <rep.dot.nop@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] svn commit: trunk/uClibc: ldso/include ldso/ldso/sparc	libc/string etc...
Date: Sat, 15 Sep 2007 21:21:54 +0200	[thread overview]
Message-ID: <20070915192154.GL20058@aon.at> (raw)
In-Reply-To: <f43fc5580709150607t4e51b73by878a54e35da00750@mail.gmail.com>

On Sat, Sep 15, 2007 at 04:07:12PM +0300, Blue Swirl wrote:
>On 9/15/07, Bernhard Fischer <rep.dot.nop@gmail.com> wrote:
>> On Sat, Sep 15, 2007 at 12:50:59AM -0700, vapier at uclibc.org wrote:
>> >Author: vapier
>> >Date: 2007-09-15 00:50:58 -0700 (Sat, 15 Sep 2007)
>> >New Revision: 19840
>> >
>> >Log:
>> >Blue Swirl writes:
>> >I got the library to compile with the attached patches, though dynamic
>> >loader crashes early.
>> >
>> >In buildroot I changed the architecture name by hand from sparc to
>> >sparc64, otherwise the compiler produced 32-bit files with V9 (64-bit)
>> >instructions. This configuration is not supported by QEMU, so I aimed
>> >for pure 64-bit. I think Sparc64 option needs to be added to
>> >buildroot.
>>
>> http://buildroot.uclibc.org/cgi-bin/viewcvs.cgi?rev=19853&view=rev
>>
>> Blue Swirl, please let me know if that's correct and useable now.
>
>The CPU selection could be improved so that for Sparc64, only the
>following are valid:
>config BR2_sparc_v9
>config BR2_sparc_ultrasparc
>config BR2_sparc_ultrasparc3
>config BR2_sparc_niagara

Ok, will do.

>I'm not so sure about removing those from Sparc(32) options, because
>then we could not build a 32-bit environment for V9 CPU.

In uClibc, we have v7, v8, v9, v9b (?).
What is the relation between insn-set/insn scheduler for these:
sparclite:      f930, f934, sparclite86x
sparclet:       tsc701
Are these all v8 (for uClibc)?

And what is v9b? An extended insn set or just v9 with a different
scheduling?

>I'm just trying a native build, looks like the compiler options build
>are not correct, there is -mcpu=v7 flag even though I selected v9.

Sounds odd, i'll look into this.

  parent reply	other threads:[~2007-09-15 19:21 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 [this message]
2007-09-15 19:41       ` Blue Swirl
2007-09-15 22:27         ` Bernhard Fischer
2007-09-16 21:25           ` [Buildroot] sparc64 v9 VIS toolchain bug with fzeros? Bernhard Fischer
2007-09-17 17:21             ` 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=20070915192154.GL20058@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.