From: Thorsten Glaser <tg@mirbsd.de>
To: debian-68k@lists.debian.org
Cc: linux-btrfs@vger.kernel.org,
Linux Kernel Development <linux-kernel@vger.kernel.org>
Subject: Re: btrfs zero divide
Date: Tue, 30 Jul 2013 15:40:01 +0000 (UTC) [thread overview]
Message-ID: <Pine.BSM.4.64L.1307301539150.28836@herc.mirbsd.org> (raw)
In-Reply-To: <alpine.DEB.2.02.1307301052010.23107@ayla.of.borg>
Geert Uytterhoeven dixit:
> 0: 222e ff74 movel %fp@(-140),%d1
> 4: 2a2e ff5c movel %fp@(-164),%d5
> 8: 2c2e ff60 movel %fp@(-160),%d6
> c: 4c45 1402 < divul %d5,%d2,%d1 >
> 10: 2d40 ff64 movel %d0,%fp@(-156)
> 14: 2d41 ff68 movel %d1,%fp@(-152)
> 18: 2205 movel %d5,%d1
> 1a: 4c2e 1800 ff68 mulsl %fp@(-152),%d1
> 20: 4c04 0800 mulsl %d4,%d0
> 24: 2041 moveal %d1,%a0
> 26: d1c0 addal %d0,%a0
> 28: 2206 movel %d6,%d1
> 2a: 4c2e 1400 ff68 mulul %fp@(-152),%d0,%d1
This is gcc-4.8 compiled, btw… in case that’s a known issue.
bye,
//mirabilos
--
“It is inappropriate to require that a time represented as
seconds since the Epoch precisely represent the number of
seconds between the referenced time and the Epoch.”
-- IEEE Std 1003.1b-1993 (POSIX) Section B.2.2.2
next prev parent reply other threads:[~2013-07-30 15:54 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.BSM.4.64L.1307300820160.20675@herc.mirbsd.org>
2013-07-30 9:07 ` btrfs zero divide (was: Re: Linux 3.10 problem reports (yes, plural)) Geert Uytterhoeven
2013-07-30 15:40 ` Thorsten Glaser [this message]
2013-07-30 17:13 ` Josef Bacik
2013-07-30 17:36 ` Joe Perches
2013-07-30 19:02 ` btrfs zero divide Thorsten Glaser
2013-07-30 20:40 ` Josef Bacik
2013-07-30 21:05 ` Joe Perches
2013-07-30 21:25 ` Thorsten Glaser
2013-08-08 20:01 ` Thorsten Glaser
2013-08-09 12:26 ` Andreas Schwab
2013-08-09 12:30 ` Andreas Schwab
2013-08-09 14:35 ` Josef Bacik
2013-08-13 12:12 ` Geert Uytterhoeven
2013-08-09 18:04 ` Zach Brown
2013-08-13 16:32 ` Geert Uytterhoeven
2013-08-14 8:40 ` Geert Uytterhoeven
2013-08-14 8:56 ` Geert Uytterhoeven
2013-08-14 18:07 ` Joe Perches
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=Pine.BSM.4.64L.1307301539150.28836@herc.mirbsd.org \
--to=tg@mirbsd.de \
--cc=debian-68k@lists.debian.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-kernel@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;
as well as URLs for NNTP newsgroup(s).