From: Ullrich von Bassewitz (uz_at_musoftware.de)
Date: 2002-12-04 12:49:37
Hi!
(BTW: The timestamp recorded in your mails seems to be off by one hour)
On Wed, Dec 04, 2002 at 11:54:26AM +0100, Groepaz wrote:
> btw speaking of the docs...IMHO there should be a special section "for former
> tasm (and simelar) users" that describes how to use ca65 in the most
> "tasm-ish" way. (ie, many ppl i have been telling to use ca65 were switching
> assemblers not because they were missing features, but because their old
> assembler had obscure bugs - and is no more developed for that matter).
Yes, it would be useful, like a whole bunch of other things. Fact is that I'm
not able to do that, because my time is limited. I'm already way behind with
other cc65 stuff, and I'm currently spending a lot of time working on the
compiler. With new libraries, new features, more doc files that have to be
updated, it becomes more and more difficult to keep all this up to date. There
will probably be a new compiler release in about 7 days - going out with known
bugs, because I'm not able to fix them before the release date. Christian and
Maciej are doing a great job maintaining the Atari and GEOS parts, and I'm
very glad about the solid and steady work. But please remember that the
complete remainder, that is: all CBM platforms, the compiler, linker,
assembler, archiver, most of the shared runtime and C library, new APIs like
the graphics and extended memory API, and a lot of design work are my part.
While I'm currently able to spend a substantial amount of time on cc65, this
will change soon, so I cannot start anything new now.
> however, if you would like to add sth like that to the docs, i'd volunteer to
> write it ... i can probably cut'n'paste it from my emails anyway :o)
I'm alsways glad about contributions. Please have a look at the existing docs
and create yours in a similar way. Which means: Use SGML and the LinuxDoc
style and try to make it fit into the existing documentation.
> yeah, looks good... i'll start with making my mind up about how to implement
> this at ALL hehehe :o)
I've started a simulator a long time ago, but I never had the time to work on
it since then (see above for possible reasons). My plan was to create a
virtual 6502 machine that is specially crafted to work as a debugger in a
hosted environment (and NOT to emulate an existing machine). It would load
modules (dynamic libraries) to implement memory areas, I/O chips and such, so
the actual memory layout can be adjusted to the code. Using printf would write
to stdout of the simulator process and reading from stdin would read from
stdin of the process, so it would be possible to feed test code and data to
this simulator in an easy way and check the output for any problems. Doing
this, tests could be automated and a test suite could be developed that is run
over the compiler before a release.
> after a quick peek... i wouldnt mind ALL filenames written by their absolute
> pathes. :) (else the debugger for example needs to know about the location of
> the library sources).
This does not really help, since most people will link against runtime
libraries not created on their system. Use the filenames as is and add
additional directories that can be searched for files. If this shows up to be
a real problem, THEN the time is come to think about another solution.
> also, i think the file should tell the total memory used by the program (maybe
> splitted into bss/code/data etc) so the debugger can use that, and the the
> addr2line info for calculating areas for which is no debug-information
> available, but which are still code. (is that even a possible scenario incase
> of cc65? mmmh)
Since all symbols are available to the debugger, it is easy to access
__RAM_START__ and friends to get information about the memory layout.
> oh and apropos label files.... is there a way to get ALL labels written there,
> not just the exported ones?
See debugging.sgml - you have to use the "-g" switch when compiling.
Regards
Uz
--
Ullrich von Bassewitz uz_at_musoftware.de
----------------------------------------------------------------------
To unsubscribe from the list send mail to majordomo_at_musoftware.de with
the string "unsubscribe cc65" in the body(!) of the mail.
This archive was generated by hypermail 2.1.3 : 2002-12-04 12:49:44 CET