From: Jan Pohanka <xhpohanka@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] libev on armv5 - illegal instruction
Date: Fri, 10 Aug 2012 12:57:57 +0200 [thread overview]
Message-ID: <op.witnevwzyxxkfz@pohanka-pc> (raw)
In-Reply-To: <op.witdwcuqyxxkfz@pohanka-pc>
Hi,
> working host (Ubuntu 11.10) uname -a
> Linux linux-dev 3.0.0-23-server #39-Ubuntu SMP Thu Jul 19 19:37:41 UTC
> 2012 x86_64 x86_64 x86_64 GNU/Linux
>
> my workstation (Ubuntu 12.04 lts) uname -a
> Linux pohanka-pc 3.2.0-27-generic #43-Ubuntu SMP Fri Jul 6 14:25:57 UTC
> 2012 x86_64 x86_64 x86_64 GNU/Linux
>
> It is really weird. I cannot imagine how buildroot using the same
> crosscompiler can produce different binaries on different PCs...
>
I have checked it once more with fresh git clones of BR and cross
toolchain reinstalled.
config.log in output/build/libev-4.11 are the same on both machines as
well as generated Makefiles (except of absolute paths to buildroot
directory).
However the compiled binaries on both hosts are different. I have never
seen that before.
The problem is in the function
ev_tstamp ev_time (void)
{
struct timeval tv;
gettimeofday (&tv, 0);
return tv.tv_sec + tv.tv_usec * 1e-6;
}
where the computation uses vldr instruction. I was not succesful to
simulate outside of libev...
regards
Jan
--
Tato zpr?va byla vytvo?ena p?evratn?m po?tovn?m klientem Opery:
http://www.opera.com/mail/
next prev parent reply other threads:[~2012-08-10 10:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-09 9:43 [Buildroot] libev on armv5 - illegal instruction Jan Pohanka
2012-08-10 6:58 ` Thomas Petazzoni
2012-08-10 7:32 ` Jan Pohanka
2012-08-10 10:57 ` Jan Pohanka [this message]
[not found] ` <op.witduljwyxxkfz@pohanka-pc>
2012-08-10 19:56 ` Thomas Petazzoni
2012-08-13 6:52 ` Jan Pohanka
2012-08-15 12:45 ` Jan Pohanka
2012-08-15 14:56 ` Thomas Petazzoni
2012-08-16 8:49 ` Jan Pohanka
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=op.witnevwzyxxkfz@pohanka-pc \
--to=xhpohanka@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox