OSDK Said Syntax At Line 1 Error But C Programming All Syntax Is Correct

[basicprogrammer30]

@kerravon86 I Tried To Parse C Program FIle To Tradional OS Assembly Language But Show Syntax Error:

firstperson@Acer-Aspire-4749Z:~/osdk/build$ ./bin/osdk simpleos.c
[OSDK] Compiling simpleos.c...
Error at line 1: syntax error
[ERROR] Compilation failed.
firstperson@Acer-Aspire-4749Z:~/osdk/build$ cat simpleos.c
void main() {
    // There Is Blank
}

firstperson@Acer-Aspire-4749Z:~/osdk/build$

And I want gcc like error catching system

I Think Problem Is Located In ./lang/cparser.y Line Around 250

Please Commit The Repo On compiler branch
GNU Flex Docs: https://ftp.gnu.org/old-gnu/Manuals/flex-2.5.4/flex.html

[kerravon86]

Sorry - I don't understand. I can see that you are trying to compile a C program. Presumably you want to generate x64 assembler output, correct? What is the reason you don't simply use gcc to do that?

[basicprogrammer30]

yes. but try compile using gcc and osdk

[kerravon86]

yes. but try compile using gcc and osdk

I'm not sure I understand. Are you trying to use gcc UNDER osdk? You showed what looks to be a Linux prompt. You're not using osdk. gcc under Linux normally works fine. Why aren't you simply using it? What are you doing that adds some value to that normal process?

[basicprogrammer30]

I Don't Use GCC Source Code Because I Can't Easily Implement Low Level Language Because It's Complex (More Stepper Learning Curve) (Time Consuming) And GCC Is Heavyweight.

[kerravon86]

I Don't Use GCC Source Code Because I Can't Easily Implement
Low Level Language

I don't know what you're calling a "low level language". I can see
from the source code you tried to compile what looks like C code.

GCC will totally compile C source code. So I don't understand
what you are trying to do.

Then you use the word "implement". What do you mean by this?
How do you "implement a language"? You mean you want to write
a brand new compiler for a brand new language? Or a brand new
compiler for C?

Because It's Complex (More Stepper Learning Curve)
(Time Consuming) And GCC Is Heavyweight.

You mean the GCC source code itself is complex? Why do you
care about that? Are you planning on modifying it? Is there
something wrong with it that would make you want to modify it?

It already produces x64 assembler code. I'm not sure what else
you would want from a theoretical replacement.

[basicprogrammer30]

You’re actually asking the right questions — the distinction here is subtle but important.

Let’s unpack what’s going on conceptually when someone says:

“I don’t want to use GCC’s source because it’s too complex — I want to implement my own low-level language compiler.”

---

🧩 What They Usually Mean by “Low-Level Language” Here

When people in OS-dev talk about “low-level language”, they usually mean:

“A language that maps almost directly to CPU instructions or to a kernel environment, without depending on an operating system or libc.”

That doesn’t mean it’s assembly — it means:

• No syscalls, no malloc(), no file I/O.

• The language gives direct control over memory, interrupts, and hardware.

• The compiler emits code suited for a bare-metal context (no OS).

GCC can generate bare-metal code if you configure it carefully, but it was never designed to be simple or customizable for people writing their own languages or experimental OS kernels.

---

⚙️ Why Someone Might “Implement” Their Own Compiler Instead of Using GCC

“Implementing a language” means:

• Writing a compiler or interpreter that translates a new syntax into machine code (or into assembler, or into C).

• It’s like writing your own mini-C, or a C-subset, or something domain-specific like “kernel-C”.

Reasons someone might do this:

Motivation	Explanation
🧠 Learning	Building a compiler teaches parsing, codegen, and CPU internals.
🧩 Control	They can design syntax that fits their OS or hardware model directly (e.g., interrupt void isr0()).
⚙️ Simplicity	GCC’s build system and backend are massive; a small project might need just a tiny subset.
🚀 Speed / Size	A 100 KB custom compiler can target 16-bit or microcontroller systems where GCC doesn’t fit.
🧬 Experimentation	Try new language ideas, e.g., inline boot directives, task keywords, etc.
🪶 Integration	A self-contained compiler can emit flat binaries or disk images directly, which GCC doesn’t do.

---

If you’re mostly trying to learn or experiment, writing your own small compiler (your OSDK) around or instead of GCC is an excellent educational path.

If you just need to build software efficiently, then yes — stick with GCC or Clang and save yourself the engineering time.

Would you like me to show you what a minimal “low-level C subset” compiler might look like — something that translates int main() { return 42; } directly into x86 machine code in under 200 lines?

[basicprogrammer30]

You Not Needed To Implement Assembler Manually. Please Use LLVM Assembler