diff options
author | Kartik Agaram <vc@akkartik.com> | 2019-05-18 00:00:18 -0700 |
---|---|---|
committer | Kartik Agaram <vc@akkartik.com> | 2019-05-18 00:45:12 -0700 |
commit | 83c67014034bbf9072d7e4555b0e51e815a95756 (patch) | |
tree | cf52127783efc20bbe8d903d96e73bc51a1f752d /subx/Readme.md | |
parent | 4b506b630ce28b3574a9f903904588f92dd3a1c1 (diff) | |
download | mu-83c67014034bbf9072d7e4555b0e51e815a95756.tar.gz |
switch to new syntax for segment headers in C++
Diffstat (limited to 'subx/Readme.md')
-rw-r--r-- | subx/Readme.md | 7 |
1 files changed, 4 insertions, 3 deletions
diff --git a/subx/Readme.md b/subx/Readme.md index c91d10ab..cab1a503 100644 --- a/subx/Readme.md +++ b/subx/Readme.md @@ -243,10 +243,11 @@ Use it now to follow along for a more complete tour of SubX syntax. SubX programs map to the same ELF binaries that a conventional Linux system uses. Linux ELF binaries consist of a series of _segments_. In particular, they distinguish between code and data. Correspondingly, SubX programs consist of a -series of segments, each starting with a header line: `==` followed by a name. -The first segment must be named `code`; the second must be named `data`. +series of segments, each starting with a header line: `==` followed by a name +and approximate starting address. -Execution begins at the start of the `code` segment by default. +All code must lie in a segment called 'code'. Execution begins at the start of +the `code` segment by default. You can reuse segment names: |