2023年1月18日(水) 0:49 JOHN DIMEGLIO johnd007@users.sourceforge.net: I don't know, why would the asm68c 6800 assembler cause the software to go into a (not responding) mode or freeze up, when after initiating a compile of a 6800 assembly program? Well, help me out here, I need more information. For starters, what operating system are you using? Also, what C compiler did you use to compile the assembler? What warnings and errors did the compiler tell you when you compiled it? And, how are you invoking...
I don't know, why would the asm68c 6800 assembler cause the software to go into a (not responding) mode or freeze up, when after initiating a compile of a 6800 assembly program? My email address: johndimeglio957@yahoo.com. Thank you.
2022年9月17日(土) 15:04 Richard Rothwell chergr@users.sourceforge.net: Hi, Hi, and thanks. I can run figforth on the simulator fine. Except typing WORDS look like this. WWOORRDDSS Typing backspace backspaces 5 characters. This does not occur in the exorsim monitor, so I figure its an issue with the forth and its adaption to call EXBUG for EMIT and KEY. I have not diagnosed this properly yet, but though you might like to know, To tell you the truth, I haven't properly worked out how the EXORsim terminal...
Hi, I can run figforth on the simulator fine. Except typing WORDS look like this. WWOORRDDSS Typing backspace backspaces 5 characters. This does not occur in the exorsim monitor, so I figure its an issue with the forth and its adaption to call EXBUG for EMIT and KEY. I have not diagnosed this properly yet, but though you might like to know,
Home
Home
List switches, .bin and .c10 output formats
Now assembles Tom Pittman's Tiny BASIC (Holger Veit transcription)
adding semicolon comments, etc.
lengthening the labels so tiny basic can assemble
Maybe I can assemble stdin now?
now assembles most of tiny basic
bring in the 6801 version forth
Correcting asmspec
Okay, I finally got the proper fix for this into the repository.
Fix an outstanding bug in strsave()
adding a socialized fig-forth for people's convenience.
socialize.pl is now just for converting counted strings to quoted.
Fixing the FCC handling.
And likewise. Sorry I was so slow to take a real look at it. It'll be a few weeks, at least, before I can push a fix in. Wish I had more time to work on it. Want to set it up to handle some of the other Motorola 8-bit processors, but I'd probably do better to rewrite it from scratch.
On the other hand, 2017/08/10 3:53 "Ron Yorston": Here's a really, really basic source file: FLAG EQU $E084 FIRST EQU $15CF This produces output like: | 15cf:FIRST || 15cf:FIRST || e084:FLAG | | e084:FLAGa | where the second, duplicated symbols have a surplus character appended. Sometimes printable, sometimes not. And sometimes the assembler crashes without any output. This is on Linux: Fedora 26. There's only one use of the macro mystrcpy, in strsave. length+1 bytes are allocated for newword and...
On the other hand, 2017/08/10 3:53 "Ron Yorkston": Here's a really, really basic source file: FLAG EQU $E084 FIRST EQU $15CF This produces output like: | 15cf:FIRST || 15cf:FIRST || e084:FLAG | | e084:FLAGa | where the second, duplicated symbols have a surplus character appended. Sometimes printable, sometimes not. And sometimes the assembler crashes without any output. This is on Linux: Fedora 26. There's only one use of the macro mystrcpy, in strsave. length+1 bytes are allocated for newword and...
Thanks for looking at this. On Fedora 26 I have gcc 7.1.1 and glibc 2.25. It's a 64-bit system. I've now built and used the assembler on a 32-bit CentOS 6 system with gcc 4.4.7 and glibc 2.12. In this case my source assembled without incident. Clearly it's system-dependent. On both Fedora and CentOS Valgrind identifies the problem. With my suggested change to the macro Valgrind doesn't report any runtime errors.
On the other hand, 2017/08/10 3:53 "Ron Yorston" rmyorston@users.sf.net: Here's a really, really basic source file: FLAG EQU $E084 FIRST EQU $15CF This produces output like: | 15cf:FIRST || 15cf:FIRST || e084:FLAG | | e084:FLAGa | where the second, duplicated symbols have a surplus character appended. Sometimes printable, sometimes not. And sometimes the assembler crashes without any output. This is on Linux: Fedora 26. There's only one use of the macro mystrcpy, in strsave. length+1 bytes are allocated...
This is very odd. I don't see this behavior on my system -- Debian Wheezy, gcc 4.7.2 as of now. If you look at, say, fig-forth/fig-forth.list.goal, you should be able to see the results I get. I hope you'll be patient with me about this, because it would be a big favor if I could ask you to descend into the test-stuff directory and the fig-forth directory and do a make and make test in each of those, preferably with a fresh copy of the source, and tell me what the diffs say. And I've left this out...
Here's a really, really basic source file: FLAG EQU $E084 FIRST EQU $15CF This produces output like: | 15cf:FIRST || 15cf:FIRST || e084:FLAG | | e084:FLAGa | where the second, duplicated symbols have a surplus character appended. Sometimes printable, sometimes not. And sometimes the assembler crashes without any output. This is on Linux: Fedora 26. There's only one use of the macro mystrcpy, in strsave. length+1 bytes are allocated for newword and the macro is invoked as: mystrcpy(newword, oldword,...
Thanks for giving the assembler a try. My 6800 source code is not producing any writes beyond allocation. Could you show some of your lines where this occurs, and describe the output you are getting?
Thanks for releasing this assembler. I tried it with some of my 1983-vintage code and found a problem: when the mystrcpy macro pre-terminates the new string it writes beyond the end of the allocated buffer.
Getting a start on emulation.
More of the mnemonics table split (svn habits a...
Split the mnemonics table out to make it more a...