diff options
| author | Kartik Agaram <vc@akkartik.com> | 2019-02-13 00:01:14 -0800 |
|---|---|---|
| committer | Kartik Agaram <vc@akkartik.com> | 2019-02-13 00:01:14 -0800 |
| commit | a630d7fb9666bbacdd714ddc12d3c42ef1466ba7 (patch) | |
| tree | c265456ff5ff1b576b2c26251b9c32ba7eb8b38a /subx/Readme.md | |
| parent | ac73f9caf3cd0e9f8ea112394955a8c9bc18ac88 (diff) | |
| download | mu-a630d7fb9666bbacdd714ddc12d3c42ef1466ba7.tar.gz | |
4959
It's always seemed ugly to explain the rules for segment names. Let's just always require a fixed name for the code and data segments.
Diffstat (limited to 'subx/Readme.md')
| -rw-r--r-- | subx/Readme.md | 3 |
1 files changed, 1 insertions, 2 deletions
diff --git a/subx/Readme.md b/subx/Readme.md index de7a0fa7..b03176f0 100644 --- a/subx/Readme.md +++ b/subx/Readme.md @@ -274,8 +274,7 @@ 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 is assumed to be for code, and the second for data. By -convention, I name them `code` and `data`. +The first segment must be named `code`; the second must be named `data`. Execution always begins at the start of the `code` segment. |