From: Petr Stehlik <pstehlik@sophics.cz>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: debian-68k@lists.debian.org, Linux/m68k <linux-m68k@vger.kernel.org>
Subject: Re: new ARAnyM with better FPU
Date: Tue, 27 Mar 2012 10:06:25 +0200 [thread overview]
Message-ID: <1332835585.6243.45.camel@petr> (raw)
In-Reply-To: <CAMuHMdVegR=pb_JPYH_PBWjYCZzt0Ga4jgFdTcFjEuyxhm_DJQ@mail.gmail.com>
Geert Uytterhoeven píše v Po 26. 03. 2012 v 22:41 +0200:
> Bad news:
>
> aranym_0.9.12-1.lucid_amd64.deb: du works
> aranym_0.9.13-1.lucid.mpfr4_amd64.deb: du fails with "memory exhausted",
> just like in 0.9.9.
Hmm. The difference between those two particular packages is that the
latter has the new MPFR FPU that should have been better than the one in
previous versions (otherwise Andreas wouldn't bother implementing it, I
believe).
Could you please try building the http://packages.debian.org/sid/aranym
that contains a patch for another post-release FPU bugfix? If that
doesn't help then feel free to stay with 0.9.12 as it contains the CPU
CAS fixes and also the proven FPU.
Andreas is reading this for sure so he might have a clue about the
failing 'du' with MPFR FPU emulation as well.
Petr
next prev parent reply other threads:[~2012-03-27 8:06 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-20 22:24 new ARAnyM with better FPU Petr Stehlik
[not found] ` <Pine.BSM.4.64L.1203210905300.23907@herc.mirbsd.org>
2012-03-21 9:34 ` Petr Stehlik
2012-03-21 10:08 ` Geert Uytterhoeven
2012-03-21 13:41 ` Petr Stehlik
2012-03-21 15:08 ` Geert Uytterhoeven
2012-03-21 18:33 ` Petr Stehlik
2012-03-21 18:44 ` Thorsten Glaser
2012-03-23 12:26 ` ARAnyM 0.9.13 with MPFR even for Lucid Petr Stehlik
2012-03-23 14:54 ` Thorsten Glaser
2012-03-25 9:55 ` Geert Uytterhoeven
2012-05-06 23:38 ` Thorsten Glaser
2012-03-26 20:41 ` new ARAnyM with better FPU Geert Uytterhoeven
2012-03-27 8:06 ` Petr Stehlik [this message]
2012-03-27 15:24 ` Andreas Schwab
2012-03-29 10:49 ` Petr Stehlik
2012-05-06 23:19 ` Thorsten Glaser
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=1332835585.6243.45.camel@petr \
--to=pstehlik@sophics.cz \
--cc=debian-68k@lists.debian.org \
--cc=geert@linux-m68k.org \
--cc=linux-m68k@vger.kernel.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