[PUZZLE] Binary-to-decimal Golf Challenge (fixed; please retry)

Cluso99 · 2012-05-15 22:38

And here is a faster version (tables are generated, but not the inline code)

Total cog (hub) space = 139 longs, times 31/103/64
Total cog incl res is 239 longs

bin2dec_golf_v4_cluso[faster3].spin

SRLM · 2012-05-16 00:41

Cluso99 wrote: »

I could not think of a way to report the "res" usage. Any ideas???

You could have a label before and a label after the user RES declarations, and subtract the addresses to get the length. Wouldn't that work?

Cluso99 · 2012-05-16 01:03

SRLM wrote: »

You could have a label before and a label after the user RES declarations, and subtract the addresses to get the length. Wouldn't that work?

No... that is what I tried without success

kuroneko · 2012-05-16 01:18

Cluso99 wrote: »

No... that is what I tried without success

Not perfect but usable:

PUB getSize

  return tail

DAT
start           res     24
tail            long    $ - start

Cluso99 · 2012-05-19 02:19

Here's another...
61 longs (hub) + 4 "res" longs: 43/191/79

It's really interesting. The data set has a lot to do with the code that produces the fastest results!

bin2dec_golf_v4_cluso[small4].spin

[PUZZLE] Binary-to-decimal Golf Challenge (fixed; please retry)

Comments