flat assembler
Message board for the users of flat assembler.

Index > Linux > sweet spot to publish assembly code paths

Thread Post new topic Reply to topic

Joined: 23 Oct 2020
Posts: 371
Location: Marseille/France
sylware 05 Nov 2023, 18:22
Dumping in one repos many, intermangled, and often dependent, assembly code paths does not feel right. Usually, I only want a one or very few without pulling the whole "lib" (for instance the heavy thing).

I would prefer very few code paths (usually very related), or even only one with significant added value (for instance a getopt_long "enough" compatible with glibc one), in one repo (usually a public git). With an idiotic and small build shell script, to output a ELF object file... but the source code should try to be compatible with a "One Assembly Unit" (names and symbols proper mangling with a simple pre-processor).

If a code path would require services from other code paths, better go with very standard functions which you can parameter their names very easily (to ease "One Assembly Unit" support, ELF object symbol names...)

I guess I'll try to do that in the future.
Post 05 Nov 2023, 18:22
View user's profile Send private message Reply with quote
Display posts from previous:
Post new topic Reply to topic

Jump to:  

< Last Thread | Next Thread >
Forum Rules:
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You cannot attach files in this forum
You can download files in this forum

Copyright © 1999-2023, Tomasz Grysztar. Also on GitHub, YouTube.

Website powered by rwasa.