8 Dec
2005
8 Dec
'05
6:43 p.m.
On Dec 8 2005, 16:26, Jim Leonard wrote:
Allison wrote:
1970s so my
You lived a shelterd life.
I lived a young life. I first became of programming age in late first CPUs were 6502, Z80, 68000, and 808x.
Whether it's called a Half Carry or an Auxiliary Carry seems to depend
somewhat on whose data book you read. I've seen both used for the Z80
for example, indifferent manuals.
...in a 6800, it's called the Auxiliary Carry; in a 6809 it's called a
Half Carry. It's bit 5 of the status register in both.
...in a Z80 and 8086 it's called the Auxiliary Carry; it's bit 4 in the
Flags register in these and 8080/8085.
...it's bit 5 in 8048 and 8051 series micrcontrollers.
There's no (visible) equivalent in a 6502 because of the way its
special Decimal Mode for BCD arithmetic works. Ditto for a 68000.
There isn't one in an ARM either.
--
Pete Peter Turnbull
Network Manager
University of York
8 Dec
8 Dec
8:28 p.m.
Pete Turnbull wrote:
...in a Z80 and 8086 it's called the Auxiliary
Carry; it's bit 4 in the
Always wondered what this was for :-)
--
Jim Leonard (trixter at oldskool.org) http://www.oldskool.org/
Want to help an ambitious games project? http://www.mobygames.com/
Or check out some trippy MindCandy at http://www.mindcandydvd.com/
8:28 p.m.
On 12/8/2005 at 11:43 PM Pete Turnbull wrote:
There's no (visible) equivalent in a 6502 because
of the way its
special Decimal Mode for BCD arithmetic works. Ditto for a 68000.
The 68K decides instead to dedicate special instructions (ABCD, SBCD,
NBCD). Not a bad solution, particularly with auto-increment and decrement
on the source and destination addresses.
The whole business of BCD arithmetic probably stems from the binary
paranoia exhibited in the 50's-70's by the business community. COBOL
features arithmetic directly on character strings, or in the case of IBM
comp-3 numbers, packed strings. PL/I displays the same thing. Gotta have
it because you can't represent 1/10 as a non-continuing binary fraction and
that gives rise to the story about the fellow who collected binary "round
off" error in his own bank account and got very wealthy. Forget that even
BCD has roundoff/truncation/loss of significance problems too, just give us
our decimal!
When I was designing a BASIC compiler and run-time in the 70's, it was made
very clear to me that BCD floating point was a given. No binary--it gives
business types the willies no matter how much precision you attach to it
(I'd proposed as an alternative binary with a decimal fixed point). When
8087 support was added to Supercalc, numbers were still stored internally
as BCD floating point, in spite of being handled as binary inside in the
8087.
Hopefully, we're all past that now. Maybe we can jettison the DAA, DAS,
AAM and AAD from the x86 instruction set.
ZAP,
Chuck
6873
days inactive
6874
days old
2 comments
3 participants
participants (3)
-
cclist＠sydex.com -
pete＠dunnington.plus.com -
trixter＠oldskool.org