From: Mike Frysinger <vapier@gentoo.org>
To: gdb-patches@sourceware.org
Subject: Re: [patch] sim: bfin: fix typos in large constants in tests
Date: Sun, 25 Mar 2012 07:56:00 -0000 [thread overview]
Message-ID: <201203250356.20472.vapier@gentoo.org> (raw)
In-Reply-To: <201203250242.58817.vapier@gentoo.org>
[-- Attachment #1: Type: Text/Plain, Size: 698 bytes --]
and along those lines, i've committed this as well
-mike
2012-03-25 Mike Frysinger <vapier@gentoo.org>
* fact.s: Comment out test with too large a number (6227020800).
--- fact.s 4 Jun 2011 17:44:21 -0000 1.1
+++ fact.s 25 Mar 2012 07:54:48 -0000
@@ -28,7 +28,11 @@ _test:
factorial 10 3628800
factorial 11 39916800
factorial 12 479001600
- factorial 13 6227020800
+# This is the real answer, but it overflows 32bits. Since gas itself
+# likes to choke on 64bit values when compiled for 32bit systems, just
+# specify the truncated 32bit value since that's what the Blackfin will
+# come up with too.
+# factorial 13 6227020800
factorial 13 1932053504
pass
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
prev parent reply other threads:[~2012-03-25 7:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-25 6:43 Mike Frysinger
2012-03-25 7:56 ` Mike Frysinger [this message]
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=201203250356.20472.vapier@gentoo.org \
--to=vapier@gentoo.org \
--cc=gdb-patches@sourceware.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