This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
Messages - the_mad_joob
Pages: 1 ... 16 17 [18] 19 20 ... 24
256
« on: December 09, 2011, 06:03:04 pm »
Hey guyz...
While doing some debugging with my app, i discovered that every time an off-page call is made, ram page 1 address is loaded into port 7 (right before processing the off-page code).
On the other hand, port 7 doesn't seem to be altered when returning from the call.
So, i was wondering if os routine calls have the same behaviour...
257
« on: November 25, 2011, 10:41:10 am »
> all procedures complete <
current overall size (bin) : 17830 bytes
left to do, in order :
> main code for passes 1, 2, and 3 (represents less than 10% of the whole code)
> debugging part 1
> screeny for u guyz =]
> hardware-specific include prgm(s) (basically some boring reformating job)
> debugging part 2
> find a way to code the goto feature and do it
> debugging part 3
> jp>jr optimization
> readme
> upload beta @www.ticalc.org
> create dedicated topic @www.omnimaga.org
I can make it...
258
« on: November 24, 2011, 09:24:01 am »
Some little fresh news about the project :
Current size is about 17K, and final will probably be around 20 (2 pages app confirmed).
The code part will probably be finished in a few weeks.
It took longer than expected, cuz i did lots of changes since.
I'm also optimizing the best i can, in real time (trust me, would be too dangerous to perform post-optim with such code).
The way i coded it (and if everything works as expected), asmdream should handle things such as high level language libraries (soundz juicy i know =]).
z80 ops are now hard-coded and threated using my new 4-levels indexing algorithm, which should improve the assembling speed significantly.
On the other hand, i reduced the assembler limitations to the max i could, and there's a chance it'll have a negative impact on assembling speed (definitely hope not).
It will handle up to 17 different error types.
That said, still have to find how to code a custom goto routine... (@Quigibo : help me plz you're my only lead there =])
259
« on: September 02, 2011, 06:18:48 am »
Great site.
Great community.
HB Omni =]
260
« on: August 28, 2011, 03:25:28 pm »
May be quite useful for some...
Thx 4 the share =]
261
« on: August 28, 2011, 06:12:00 am »
Simply awesome.
Thx dj, u definitely rock =]
262
« on: August 27, 2011, 04:08:21 pm »
I have no knowledge and sure dont have any coding skills to make this true.
There's a beginning for everything...
263
« on: August 21, 2011, 04:48:44 am »
Actually, using 8-bit backups uses an average of 8 t-states when it comes to half registers.
That's right, 8 t-states, but you have to consider both saving & restoring operations to really see the total time you're saving : 1 push + 1 pop = 21 ts with 2 bytes 1 ld ixx,r + 1 ld r,ixx = 16 ts with 4 bytes Half indexs are definitely cool, especially when coding without space restrictions (apps basically).
264
« on: August 20, 2011, 03:01:18 pm »
Personnaly, i often use ix half registers as 8-bit backups.
In this case, saving|restoring a value is twice as big than using the stack but when speed is the desired criteria, saving 5 t-states can definitely matter.
265
« on: August 19, 2011, 07:01:12 am »
PM sended.
Thx for the tip zippy =]
266
« on: August 19, 2011, 04:59:44 am »
Some fresh news...
After infinite failed attempts, i finally found a way to force the os to open up the prgm editor upon exiting the app.
However, since the method is quite tricky, i won't get the render i wanted.
The sequence will look like this :
- An error is encountered during the process.
- The error details are displayed.
- The curious user selects the goto option.
- The app automatically quits.
- The os immediately shows a syntax error.
- If goto is selected, the prgm editor is opened for the concerned prgm (source or include), the cursor pointing to the line where the error was encountered.
Unfortunately, here are the drawbacks :
- The ugly ERR:SYNTAX menu.
- The user will have to select the goto option twice (one time in the app and one time when back to the os).
- Not possible to point to a token, only a line (The user will have to use his brain a bit, despite i didn't wanted that).
- I will have to modify my code again =[
I wouldn't say i'm proud of it but it's better than nothing and at least, it works =]
267
« on: August 07, 2011, 01:23:29 pm »
Zstart seems to be quite a nice piece of code =]
Btw, dunno if it's related to the os version, but my clock is never affected by resets, at least ones voluntary triggered by me (defaults/ram/all).
I use our good old 2.43.
268
« on: July 30, 2011, 01:44:43 pm »
Thx =]
Did some additionnal web readings and indeed, those 2 instructions are often reffered as "null input|output instructions".
> first post edited
269
« on: July 30, 2011, 07:53:46 am »
Thanks, and yeah actually the main issue is that it's very picky about syntax and sometimes even the right ASM syntax is not supported. There are also quirks like how it can't check the last line, so you get stuff like No END directive before EOF, so you need to add an extra linebreak.
Yeah, always heard about those bugs but never had the opportunity to encounter any of them at all. I'm probably just lucky there... Actually, that should be OUT (C),0
There seem to be different schools about that one. On wikiti, it's indeed named as OUT (C),0. But, if you look closely at the op value, it's the exact opposite of IN F,(C). More precisely, the following is true for every register written|read (A|B|C|D|E|F|H|L) : IN reg,(C) > $ED,$40+ reg_opOUT (C), reg > $ED,$41+ reg_opThat's to say, the direction of the transfer is defined by the value of bit 0 on byte 2. As if it has the exact opposite effect, i honestly don't know, since i'm not familiar with those instructions. Wikiti says the value sent to port (C) "varies with cpu", which is far from being precise. Maybe noone ever realized that this value is in fact the content of tmp (as it's called on wikiti). I'm quite interested in some more in depth clarification about that one, especially since i'm currently writing my own instruction interpreter, and, will have to decide whether the better syntax should be "F" or "0".
270
« on: July 29, 2011, 07:38:12 pm »
An infinite pleasure to see ya back dj =]
Regarding tasm, it's not the first time i hear about bugs.
From my personnal experience, the only "bugs" i have ever encountered were always triggered by non-respect of the rules.
Stuff in post 1 is definitely a good example.
Anyway, i hope this topic will be useful for those who, like me, are stuck in the past =]
Pages: 1 ... 16 17 [18] 19 20 ... 24
|
Show Posts