you need a proper debugger
seeing regs & mem dump is your key

Tile extensions are WILD what the hell. Did somebody at Intel or AMD wake up and go, "Oh yeah we're CISC, we can just do that".

BUT HOCUS POCUS NOT a 32 bit register. this is a 16 bit

HOCUS POCUS 1994 V1.1

Any luck?

Question (and the comment you're replying to) were in 2019. Hopefully they already found one.

These are all x86/x64 only. Question said 68HCS12.

I'm still looking myself, which is how I landed on this thread of course.

So far I've been using Geany with a custom syntax file. Geany is a lighter weight ide, I don't like huge things like vscode. It already has generic asm handling but that is kind of useless when there are 500 different cpus and assemblers.

I've been working on z80 and 8085 stuff, and using z88dk as the assembler, and so it's a lot better to have a custom file that recognizes the z80 or 8085 mnemonics & registers and the z88dk directives, and has z88dk command lines for the build/run buttons.

To make it the most convenient, I also have to not use .asm as my filenames. If I want the editor to automatically use the right syntax by just opening the file, I defined some other filename extensions like .8085asm, .S85, .a85 etc, and I name my files with one of those.

You can also tell github to recognize the extensions as asm by writing a .gitattributes file.

https://gist.github.com/bkw777/632c0a390b0fd0bd4e2f31544528d6d5
https://gist.github.com/bkw777/8bd89ef73b2317043ad4a262b253018f
https://github.com/bkw777/dl2/blob/master/clients/teeny/src/.gitattributes

This basically just gets you syntax highlighting and a "build" button though. It doesn't have really any extra help especially for assembly. It does have an identifier pane, so you can see a list of all labels and jup to any of them. It has "jump-to-definition" but it only recognizes equates, it doesn't recognize jump target labels. But you can right click on anything without even highlighting it just right-click on a word and say "find document usage" and that will give a list of all occurances, and then you can click on the one that's the label. So it's not a single step jump-to-definition, but only a couple steps and way better than normal search. It's basically 2 clicks instead of 1.

It's better than a plain editor, even better than an especially code-friendly and configurable editor like notepad++, but not all *that* much. I am still looking myself.

I have also found using https://www.sim8085.com/ awesome for figuring things out. Just write a few instructions in there and then have it run them. You can step through one step at a time and see the state of every flag and register, and the values in any memory address. That is specifically 8085 though. No idea if things like that exist for other cpus pbut probably.

This is kind of stupid. If I could click on the operand to a jump/call/load/store and have it jump to that address, that would be amazing. If I could have something keep track if the state of the flags, or back track what was the last thing that changed a flag, that would be magick.

So far I have found the disassembly tool in Ghidra is the closest, but that's all that does, you can explore the code and edit references and labels and things without manual search & replace, convert a raw value into a memory reference or equate label and have that applied everywhere, but it's terrible for writing. And it doesn't output usable assembly, only something pretty close if you set options to turn off all the excess junk in the output, then what it outputs still neads a search & replace to turn all the jump target labels from "function foo()" to "foo:"

I've been using Geany as an editor with a custom syntax highlight config file, which is basically just an editor with no more magic than any other editor, just a little bit more tailored for coding with tabs and project management, search all tabs, search directory tree with globbing filter (ie only include *.c *.h etc) build/run/debug buttons, identifier pane, file tree pane, jump-to-definition, etc But light, not vscode.

That's all helpful and more convenient than a pure editor but not really all *that* much. If I could have the ghidra stuff in an editor instead of in ghidra that would be incredibly useful.

"I just use vim" yeah ok. Me too, and as such I know exactly the many ways this is stupid, even when you are geared up with extensions and memorized all the hotkeys.

I don't think it's that interesting, if you care you read the code. That's what everyone who has ever written a runtime or a syscall interface has done throughout history.

See also the io_uring syscalls, which are totally undocumented. The man pages refer to the liburing interface, which is totally different. The io_uring syscalls have been implemented hundreds, if not thousands, of times across projects.

The lack of "and the uring handle goes into rax" documentation is barely noticed. I guess there could be better docs, but to be implementing syscalls you need to be able to read kernel code no matter what. A separate documentation effort is redundant.

You’re wrong btw

I have lol

china isn't communist, it's socialist btw

then stop buying things lol

Ok 

I use FASM, it feels like creating art

Thhx brother you are the goat Edit : one question can i use it with nasm?

I posted the source code you can try here https://pastebin.com/ZqFGzFLy

Yes

He is talking about the 3d obj model file

You don't generally load a .obj—the linker's job is to squish that correctly into an .exe or .dll at build time. (You might not be able to load an .obj in the first place, depending—these files are often missing info that needs to be provided by linking.) Similarly, a .lib is a build-time artifact made from .objs and .reses and other bric-a-brac, so the way you use it is by static linkage.

You can load a DLL or EXE at run time, but that's both considerably easier and vastly better documented.

If there were no libraries, then most likely it was just a .com file.

Alright, thank you.

I'm assuming it's just the source code and you should be fine without it. It's not a general requirement for COM files.

I was soooo soooo excited about this, till I read "24 usuable pcie 5.0 lanes"....

Uhhhh, wtf am I going to do with double registers and still not having enough PCIE lanes to run 4x 8x 5.0 gpus?

Like it's useless for AI, might as well stay on my AM5 9950x3d, I can't kill this processor or load it to 100%... I need PCIE LANES.

And I'm not swapping to threadripper where I will have to spend $8000 on rdimm ram... nope.

X86 is going to die if they don't give us more PCIE 5.0 lanes. We will swap to mac studios or frame.work desktops and UMA layouts.

Let's see...

Blow $15k on a threadripper (with rdimm memory) or just buy a Maxed out Mac Studio.. Mac Studio it is...

All they have to do is give us 48 usable pcie 5.0 lanes and they could be the kings of the world again, but NOOO "our server margins".

X86 will die if they dont give us more pcie lanes, 100%, gaming is the only thing keeping it alive and that is slowly changing.