Search results

I thought about writing my own preprocessor too. The dream though is to have a project that can easily be compiled with both CodeWarrior and gcc, and I don't think CodeWarrior has an easy facility built into it for doing your own preprocessing -- I think it would require writing a plug-in. Plus...

That's what I may end up doing. I'm trying to be overly clever and see if there's some way I can get the same assembly code compiling in both CodeWarrior and gcc. I was hoping the docs I was reading for CodeWarrior's standalone assembler applied to classic Mac OS, because it seemed like it...

Well, I am a bit confused. The CodeWarrior documentation makes numerous references to a standalone assembler, as well as an "Assembler Guide" manual that digs into it. However, it appears the CodeWarrior Pro 4 installer just doesn't include this assembler (or at least not the image on Macintosh...

I just finally found the CodeWarrior reference CD image with all those PDFs, so I'm going to dig through those!

Hmm, I could give MPW a try, but it unfortunately uses really different syntax from GNU, which is how my code is written right now. I found a document here that suggests there's a version of CodeWarrior that uses a more GNU-like syntax: https://www.nxp.com/docs/en/reference-manual/ASMX86RM.pdf...

This ought to be an easy and dumb question, but for the life of me I can't figure it out. I want to add a 68k assembler source file to a CodeWarrior (Pro 4) project. But I can't figure out how! Am I supposed to use a .a extension for it? Regardless of what extension I do use -- and I've tried...

I'm pretty sure that by the time I was using CodeWarrior and making phat apps (and also FAT apps) I was already on PPC. I wish I remembered which version of CodeWarrior I was on back then, and still had those old projects. Sadly the SyQuest disk with all of my old stuff got lost somewhere along...

A few C99 features that CodeWarrior Pro 4 apparently does not have is variadic macros and compound literals, which is too bad because they're quite useful.

I played around with CodeWarrior 11 for a while before updating to Pro 4, mainly because I thought 11 was the last version, what with 11 being bigger than 4. (And then I realized they changed their naming scheme part way through.) Looks like Pro 4 has quite a few improvements and features. It...

I recently set up a dev environment in BasiliskII using CodeWarrior Pro 4, since it's the last to support a 68k host. Are there any advantages you see to using CodeWarrior 11 over Pro 4?

Thanks! 😄 I've come a long way since Unicycle.

Okay, here it is: https://github.com/briankendall/Profiler68 I'd love to hear if anyone other than me ever makes use of it.

Okay, I did it! I've written a sampling profiler, and I'm actually getting usable data from it. Now I can see exactly what lines of code in my game are sucking up all the time. This'll make it a ton easier to optimize. It took a bit to get it right too. My samples include not just the stored...

Yeah, I have no ambition to make a global profiler. Just one for the current application, included as a library similar to PerformLib. I might be able to sidestep the issue of different code segments, because when compiling with Retro68, it does everything as one big segment, unless you...

I think I'm getting close to finishing my Retro68 compatible sampling profiler. I have another question I'm hoping somewhere here knows the answer to. When I have an address from the Program Counter, how do I figure out what the relative address is to the segment of code its executing in...

I missed that! But yes, that explains it, and surely will make this more reliable. Thanks for pointing that out!

Ah yes, I forgot about that ResEdit extension! I actually already have it installed in one of my systems, but forget to use it. In any case, I think I've got the search for the stack offset working, using Apple's rather strange method. There very well may be a better way of doing it buried in...

@David Cook Sorry I'm not sure if this is pinging you correctly! Okay I got it. Apologies to the user whose username is simply "David" for pinging you accidentally.

@david_cook What disassembler are you using? I'm starting to suspect that Ghidra is unreliable, in that it's not getting some of the jump instructions correctly, even when I used the linked library.

Yes, I have been using the raw library, and I didn't realize some of those statements would be changed after linking. Thanks for pointing that out! I would've ended up chasing my tail for quite a while otherwise. I built the example app using MPW, so I'll try disassembling that. I believe...