Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Michael S. Zick <minimod@morethan.org>
To: buildroot@busybox.net
Subject: [Buildroot] BB update Was:  Build jobbing
Date: Sun, 29 Nov 2009 03:16:18 -0600	[thread overview]
Message-ID: <200911290316.20688.minimod@morethan.org> (raw)
In-Reply-To: <87r5rh3e8w.fsf@macbook.be.48ers.dk>

On Sun November 29 2009, Peter Korsgaard wrote:
> >>>>> "Michael" == Michael S Zick <minimod@morethan.org> writes:
> 
> Hi,
> 
>  Michael> Try:
> 
>  Michael> Lua 5.1.4  Copyright (C) 1994-2008 Lua.org, PUC-Rio
>  >> print(math.sin(garbage))
>  Michael> stdin:1: bad argument #1 to 'sin' (number expected, got nil)
>  Michael> stack traceback:
>  Michael>         [C]: in function 'sin'
>  Michael>         stdin:1: in main chunk
>  Michael>         [C]: ?
> 
> 
> I get exactly the same on BR:
> 
> sudo chroot /tmp/blah /bin/sh
> / # lua
> Lua 5.1.4  Copyright (C) 1994-2008 Lua.org, PUC-Rio
> > print(math.sin(garbage))
> stdin:1: bad argument #1 to 'sin' (number expected, got nil)
> stack traceback:
>         [C]: in function 'sin'
>         stdin:1: in main chunk
>         [C]: ?
> 

Found what might lead to the references I need:
http://www.mips.com/products/processors/32-64-bit-cores/mips32-24k/index.cfm#specifications

Which immediately shows that I made an error - about mid-page;
Just because the core has "core extend" does not mean it has 
hardware floating point.
duh...
It would seem that if you have enough gates for a pair of DSP
cores, you would have enough to "waste" a few thousand on H.F.P.

I'll dig into the problem and try to sort it all out today.
Will also try to figure out why I didn't get a backtrace from
a NaN error in Lua.  The "no backtrace" is a separate problem
from "no double" number type.

At first glance, it looks like a case for a Config.in.mips sub-menu.
Just to get all of the gcc options and core options to match up.

Mike

  parent reply	other threads:[~2009-11-29  9:16 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-27 21:22 [Buildroot] Build jobbing Michael S. Zick
2009-11-27 21:56 ` Peter Korsgaard
2009-11-27 22:10   ` Michael S. Zick
2009-11-27 22:16     ` Michael S. Zick
2009-11-27 22:33       ` Michael S. Zick
2009-11-27 22:45         ` Michael S. Zick
2009-11-27 22:59           ` Michael S. Zick
2009-11-28 10:40       ` Peter Korsgaard
2009-11-28 10:45     ` Peter Korsgaard
2009-11-28 11:10       ` Michael S. Zick
2009-11-28 11:38         ` Michael S. Zick
2009-11-28 18:58           ` Michael S. Zick
2009-11-28 14:07     ` Peter Korsgaard
2009-11-28 14:13       ` Michael S. Zick
2009-11-28 15:35         ` [Buildroot] BB update Was: " Michael S. Zick
2009-11-28 15:43           ` Michael S. Zick
2009-11-28 19:06             ` Peter Korsgaard
2009-11-28 19:15               ` Michael S. Zick
2009-11-28 19:20                 ` Peter Korsgaard
2009-11-28 19:06           ` Peter Korsgaard
2009-11-28 19:17             ` Michael S. Zick
2009-11-28 19:41               ` Michael S. Zick
2009-11-28 20:30                 ` Peter Korsgaard
2009-11-28 21:16                   ` Michael S. Zick
2009-11-28 22:44                     ` Peter Korsgaard
     [not found] ` <200911281650.44375.minimod@morethan.org>
     [not found]   ` <87r5rh3e8w.fsf@macbook.be.48ers.dk>
2009-11-29  9:16     ` Michael S. Zick [this message]
     [not found] ` <200911290302.13984.minimod@morethan.org>
     [not found]   ` <87my253d8o.fsf@macbook.be.48ers.dk>
2009-11-29  9:31     ` Michael S. Zick
2009-11-29 10:23       ` Peter Korsgaard
2009-11-29 10:53         ` Michael S. Zick
2009-11-29 11:23           ` Michael S. Zick
2009-11-29 12:54           ` Michael S. Zick
2009-11-29 16:50           ` Michael S. Zick
2009-11-29 18:11             ` Michael S. Zick

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=200911290316.20688.minimod@morethan.org \
    --to=minimod@morethan.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox