about summary refs log tree commit diff stats
path: root/002test.cc
diff options
context:
space:
mode:
authorKartik Agaram <vc@akkartik.com>2019-07-15 12:26:41 -0700
committerKartik Agaram <vc@akkartik.com>2019-07-15 12:26:41 -0700
commitaef4efb959b215a2cd830e186c083c78f7bde60a (patch)
treead3735842abc8de847ef407a83915cae4a54c26d /002test.cc
parent867894b3efdc9c9df39d8ad9b6011f01e95e2811 (diff)
downloadmu-aef4efb959b215a2cd830e186c083c78f7bde60a.tar.gz
5404 - subx/examples/ex1 now translating
The result isn't an identical binary to before, and it segfaults when
run. But it's bugfix seven.

A couple of places where we make .subx files a little more strict:

a) All .subx files must define a data segment. Even if they have no
data.

b) All .subx files must define an `Entry` label for the binary to start
at. Earlier we used to default to the start of the code label. That's
not too hard to add; we'd just need to:
  i) rename `get` to `get-or-abort`
  ii) clone a third variant of `get-or-insert` called `get` that returns
     null if the key is not found.
  iii) use `get` rather than `get-or-abort` when looking up the `Entry`
     label.
Diffstat (limited to '002test.cc')
0 files changed, 0 insertions, 0 deletions
124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208
id='n204' href='#n204'>204