|
a glow in the dark by Sensenstahl [web]
[nfo]
|
||||||||
|---|---|---|---|---|---|---|---|---|
|
|
|||||||
|
popularity : 54% |
|||||||
alltime top: #9839 |
|
|||||||
|
||||||||
added on the 2012-03-04 22:28:35 by sensenstahl  |
||||||||
popularity helper
comments
Nice! Can be done in about 128b though.
frag: i have no doubt and it is kinda depressing to see so much crazy code while i am glad to get stuff from rough versions down from 300+ into 256. but 128b with this is not reachable for me at the moment. i can't think enough in abstract ways i guess -.- hopefully i can one day :D
RULEZ!
@frag: make a 128b demo about it :)
@frag: make a 128b demo about it :)
nice!
why not :)
this is likable too
nice one.
sensenstahl: take a look at this one - comes with all stages of optimization. i'm far from being the best 256b coder out there, but i guess i'm not the worst one either ;) i hope it'll give you some ideas. one of the nifty tricks out there is to assume the contents of some registers at the beginning - makes stuff work under windows only in some cases, but it seems noone cares anyway. second thing, take a look at nasm docs - at least older version had all opcodes documented and you can sometimes save some bytes by simply using different registers or sequence of instructions to achieve same thing. wsmz isn't optimized perfectly imho, but at the time i wrote it, it seemed good enough. keep learning and you'll get used to this sort of thinking. also, use ndisasm to see which instructions take more bytes than you think and see what you can do about it.
sensenstahl: take a look at this one - comes with all stages of optimization. i'm far from being the best 256b coder out there, but i guess i'm not the worst one either ;) i hope it'll give you some ideas. one of the nifty tricks out there is to assume the contents of some registers at the beginning - makes stuff work under windows only in some cases, but it seems noone cares anyway. second thing, take a look at nasm docs - at least older version had all opcodes documented and you can sometimes save some bytes by simply using different registers or sequence of instructions to achieve same thing. wsmz isn't optimized perfectly imho, but at the time i wrote it, it seemed good enough. keep learning and you'll get used to this sort of thinking. also, use ndisasm to see which instructions take more bytes than you think and see what you can do about it.
Love this one too
ok! could be smaller,yes!
but better reinvest found bytes into some x-movement per line!
but better reinvest found bytes into some x-movement per line!
Upside-down lillies!
ja
Sweet!
gutuntak
nice!
Interesting flowery pattern. Do more!
Cool!
YouTube: http://youtu.be/ozZ9Zx0nV-s
a blow in the dark
Wie ein Furz im Wind! Leise und erst nach einer gewissen Zeit was man ob er gut war.
Hahaha!! Looks like the rest after the pencil sharpening =).
yes
yes2
submit changes
if this prod is a fake, some info is false or the download link is broken,
do not post about it in the comments, it will get lost.
instead, click here !
A video is availiable.
Good night.