Jump to content
Have You Played Atari Today?
2600|5200|7800|Lynx|Jaguar|Forums|Store  

ggn

Members
 View Profile  See their activity

  • Content Count

    1,684

  • Joined

  • Last visited

Posts posted by ggn

  1. Posted

    This tweet tells you all you need to know about containers:

     

    This is of course the main reason we don't provide linux binaries for rmac and rln: we'd have to assume that the user links against the same version of libc we do - not a great idea.

     

    Containers for development is a weird concept: on linux you're pretty much a stone's throw away from installing dev tools and building things from source if something is missing from your setup. On Windows it's a non-issue: binary compatibility goes back decades, so there's a high chance your binary will work (worst case you have to add spefic VC runtime dlls, but those too are standarised). Unsure about macs, but the binaries for rmac/rln we create seem to work fine for people so far.

     

    While trying to add the compilers from http://brownbot.mooo.com upstream to http://godbolt.org I had to use containers to test things. It was a horrible experience: tons of MBs of things had to be downloaded and installed somewhere in the disk, and then each test I made the contained had to be spun, run, and had a really bad way to communicate errors when things went wrong. (oh yeah, containers not shutting down and remaining running without any feedback to they user were very fun things too). And of course I remember something along the lines of each time I changed something to the config of the container, it would start downloading the universe again because OMG we can't be sure what we've downloaded already, it might be different!

     

    So....... why do people even want this? Why do someone have to spin a mini VM (which is what I understand containers are) in order to just convert a couple of text files into machine language? It doesn't make much sense to me :)

     

    On most (all?) of my projects I have 0 things installed. The tools are all contained in the project (usually rmac and gfa32 which also is portable and needs no install). Worst case if I need a C compiler or whatever, I do have a ZIP file with that packed somewhere, ready to be deployed. But even that is not installed, ever.

     

    This really makes me curious to ask what people's workflows are. All I'm saying is: keep it simple, people, it's not rocket science!

  3. Posted

    Oh, floats. Well, in the past I've used https://github.com/ggnkua/pml-bigbrownbuild which is still not built using the build script. I think this repo is kind of patched up to work with newer gas format.

     

    If memory serves correct, just get this repo, cd to 'pmlsrc', edit 'Makefile.16' and 'Makefile.32' to the right paths. Then type 'make -f Makefile.16', copy the .a file somewhere, then 'make -f Makefile.32'. I cannot remember which of the two I used in the past but at least one should work.

    • Like 1

  6. Posted · Edited by ggn
    Geez, bbcode is kind of RIP

    Hello,

     

    A quick glance at the codebase (http://shamusworld.gotdns.org/cgi-bin/gitweb.cgi?p=rmac;a=blob;f=op.c;h=836f4de173b01add2b452414574c98b9c5c13953;hb=HEAD#l428)shows that the implementation of stop does not not take a parameter.

     

    We can add it easily though, no probs. As a workaround for now you can use something like the following in lieu of the stop opcode:

      

    dc.l 4<<28,O_STOPINTS

     

    (not tested, but it's probably fine)

  10. Posted

    Hi folks,

     

     

    Due to reasons I'd rather not discuss, I'm henceforth stopping all RB+ development and support. The github and bitbucket repositories will remain in place for a couple of days and will then be taken down.

     

    Thank you for all your interest in this experiment, it's been a fun 6 years. It's time to move on. Please don't PM me or ask me about this using any means, messages will be ignored.

     

     

    See you around,

    GGN

    • Like 1
    • Thanks 1
    • Confused 1
    • Sad 3

  12. Posted

    3 hours ago, SebRmv said:

    Where should I report bugs?

      

    ;;; address register = base of var array
VARREG	equ	2

.macro	emitInstr
	;; \1 = instruction
	move.w	\1,(a1)+
.endm

.macro	emitTgtMem
	;; \1 = opcode
	;; \2 = variable number (will be multiplied by 2)
	;; \3 = address register number	
	add.w	\2,\2
	beq.s	.opt\~
	emitInstr	#(\1)|(%101<<6)|((\3)<<9)
	bra.s	.done\~
.opt\~:
	emitInstr	#(\1)|(%010<<6)|((\3)<<9)
.done\~:
.endm

	;; emit "move.w #YYyy,xx(Var)"
	emitTgtMem	(%0011<<12)|(%111100),d0,VARREG

    This one produces a segmentation fault.

     

    Ok, issue found. Head over to token.h, lines 131 and 132 and change the "32" to "64". Also read the comment, you just broke a record ;).

     

    I'll have a discussion with Shamus on how to handle with this but you should be fine for now...

    • Like 1

  15. Posted

    Awww shucks guys, you're the best! I opened the page and saw half a page's worth of new messages and thought I'd have to spend a few hours testing things, but everything was resolved at the end :).

     

    A couple of notes: 

    9 hours ago, SebRmv said:

    How can I track more precisely the origin of the error?

    I thought I fixed the issues with error reporting while evaluating macros and REPTs, but it seems it's not perfect yet. I'll have another go at it. In the meantime an accurate way to pinpoint the expanding issues is to produce a listing (switch -l or -l* if you prefer no pagination).

     

    As for the rest of the patches, hopefully @Shamus will get around to integrating them into the repository so people don't have to do magic hocus pocus all the time, but grab a binary instead and do some work :)

     

    @SebRmv thanks for trying out rmac and don't hesitate to report any issues!

    • Like 1

  16. Posted

     

    2 minutes ago, pfeuh said:

    I was editing the log which was not complete.

    I assume you're trying to compile it by hand instead of using the supplied makefile? That won't work as some tools need to be built and produce some header files before the main code can be compiled.

     

    In other words, did you try typing "make"? 

  20. Posted · Edited by ggn
    BBderp

    On 7/29/2020 at 9:52 PM, dilinger said:

    Hi,
    I think I've found an issue with RLN V1.6.1.
    If the options related to symbols are not used, the PSymbolTable and NumberOfSymbols fields in the coff will still be set.
    It will create a problem if the fields are used by a tool or a debugger, because no symbols will be found in the file.
    Could it be possible to fix this problem?
    If the source code is available on Git, please let me know, I will try to have a look at the issue.

    Hi there, I've added a fix for the issue you raised on the issue tracker. If you could compile and test rln, it'd be great.

  23. Posted

    6 hours ago, poobah said:

    Used some GFA Basic back in the day, eventually started adding some asm routines before jumping ship to C. It's a really good BASIC implementation, and as others have noted, some commercial games were made with it.  Back in the day I did a Dr. Mario clone (#1 on Genie for 8 weeks... woohoo) it was in GFA Basic.

    Do you still have that? It doesn't ring a bell here!

AtariAge
Forums
Store
General
Follow AtariAge

Copyright ©1998-2021 AtariAge

×
×
  • Create New...