negative hex

This assembler uses longs (32 bit ints) internally, so if I want to plop a long into memory (.LONG) it just pokes what I type. I can imagine 0x80000000 as signed or unsigned... the assembler doesn't care. It does know how to complement and negate and stuff like that.

It treats 0x00008000 and 0x8000 as the same value, which makes sense to me.

It doesn't like to eval certain numbers as longs and then poke the low

One annoying case is making a 16-bit mask by complementing a constant, as "AND.W # ~0x2000, D3", which it tends to spike.

Since my question regards evaluating numeric values within user command strings, with no specific language or compiler implied, it makes sense to me to treat any 0xXXXX thing as positive, and any

-0xXXXX as negative. Specifically, I want users to be able to express DDS frequencies in decimal or hex, and I want them to be able to reliably select positive or negative frequencies.

John

quantity

Only if you're using 16-bit ints and decide that they are signed. I consider 0xFEEE to be decimal +65262. My HP 32S calculator agrees.

negate it.

I want "-0x40000000" to program a generator to make -16.000 MHz.

John

On a sunny day (Mon, 30 Jun 2008 11:55:27 -0700) it happened John Larkin wrote in :

Apart from connecting the '-' sign to a '-' sign in the frequency display, I have no idea what -16 MHz would be. Or shift 16 MHz down? Or 180 degrees phase flipped? What is a negative frequency?

In a DDS, negative frequency corresponds to putting a negative number into the phase accumulator. That walks a waveform table backwards. Waveforms then come out "inverted" in time. And if I create a polyphase waveform set that spins a motor clockwise, when I program the frequency to be negative, the motor will spin CCW. There are all sorts of uses for this.

It's equivalent to asking for a frequency past Nyquist, and using the resulting alias.

John

On a sunny day (Mon, 30 Jun 2008 12:43:23 -0700) it happened John Larkin wrote in :

OK, got it (I think) never too old to learn :-)

The first and second errors you made are implementing in anything other than assembler. The third was using sign magnitude.

There is good reason for that as well; it is the only system that leverages the existing ALU to the max for doing multiple byte / halfword / word / double-word and wider in a consistent manner. And you claimed to not understand hex regrouping of 2's compliment.

Actually adding sign to hex numbers will more likely confuse your users. The standard binary interpretations are far better known. (int and unsigned int)

Why don't you go whole hog and use 13's complement. See XS3 encoding.

Hmm..

One person, writing a library that has to port to 10+ CPU's, in assembler, to build the basis of number-theoretic and cryptographic functions, knowing in advance that any error in implementation will result in catastrophic security breaches...

No thanks. :)

I wrote most of it in C++, and following Donald's Knuth's admonition that...

"Premature optimization is the root of all evil."

The time-critical operations were written in assembler.

In any case, all major Big-Integer libraries follow this pattern, including the current premiere library, GMP:

Maple, OTOH, used base-10 internally for its big-number representation, IIRC from Henri Cohen's "A Course In Computational Algebraic Number Theory". That is a big mistake, IMHO.

In any case, I think you would find that the difference between C++/ assembler and assembler in terms of overall speed for the operations is minimal.

-Le Chaud Lapin-

It hasn't confused me for decades. Unlike to do so until i get senile.

2. >>>Not a negative option in sight.

Now I am confused. What is it that I claimed to not understand?

John

Really? That is very clever! And how exactly does it store -0x80000000 in a 32 bit register? Complementing it is no problem but when you add one you are back exactly where you started.

Isn't there some way of casting the bit pattern to the required size. That way by making your intentions clear the assembler knows what you want. Too many people make mistakes with byte/word/long sizes.

Yes. But you still need to give consideration to the minor boundary problem of -MAXINT-1 which for 32 bits is 0x80000000 Compliment it and add one and you will understand.

Your parser probably should not allow -0x80000000 or have the defined behaviour that -0x80000000 == 0x7FFFFFFF since the 32 bit register cannot represent +MAXINT+1

Fence post errors like this are potentially dangerous. And ambiguities in specifications are worse.

Although you don't see the problem your users might be better off if the syntax was defined to only accept values in the range 0 to 0x7fffffff if the "-" sign is used (which is what the assembler was doing)

Otherwise you have things like -0xffffffff = +1 which they may not expect even if you do!

Regards, Martin Brown

Well, I paid almost $80 for it.

It throws an error,

C:\\JOBS\\_T_SER~1\\T344\\28E344B\\28E344B.ASM(128,28): Error 36 - Operand not in specified range

which I wish it wouldn't. Assemblers should be as dumb as possible and just manipulate the bits without making value judgements. My parser never declares errors, it just moves bits.

Yup, fine by me.

Actually, I understood that ca 1968, only it was 12-bit words.

Or I can just tell the users not to do that. The maximum legal positive frequency is 31.999999985 MHz, and 0x80000000 is already -32 MHz, so requesting -(-32 MHz), -0x80000000, and getting -32 MHz isn't really outrageous.

I suppose, but it is nice to be able to set exactly 32.000000 MHz. The hex thing is mostly for "sophisticated users", of which I might someday have a few.

Good grief, another appendix to the manual.

The DDS LSB is 64MHZ * N / 2^32, which is 14.901161etc mHz. So if a user wants channel 2 to be, say, 1 KHz and asks for it that way (ascii command 2Freq 1K) and wants channel 3 to be 5 KHz (3Freq 5K), and expects to set their relative phases (simulating, say, speed pickups in a geared turbine) he'll likely notice a slow phase creep caused by rounding the Hz input to the nearest DDS LSB. So being able to access the raw DDS accumulator values is something I have to provide, and explain, already.

John

But, but - the "Sign EXtend" instruction is so much fun to code! ;-)

Cheers! Rich

Self-esteem. >:[

Thanks, Rich

They say they need a citation for the 0-9,u-z convention in the Bendix G-15 - Is just the fact that I've used one good enough? In fact, the school where I went to 11th grade had one - my first programming class was in 1965. :-)

It was a fascinating machine:

Cheers! Rich

I learned steam in Thermodynamics class. I never tried to steam myself. eSteam must be some kind of internet enabled steam engine.

And? Were does it say anything about steam?