Commit bbf785e
committed
review(coff): name /bigobj, and drop a constant the DATA rule stopped using
Two things a read-through caught.
`/bigobj` objects are a different container — machine 0 and `0xFFFF` where the
section count would be — and the reader fell through to "unsupported COFF machine
0x0000". True and useless: it blames the reader for a flag the project passed.
Named now, with the two ways out (drop /bigobj, or annotate the surface and need
no generated .def at all).
`kScnMemWrite` was left over from a first version whose DATA rule keyed on
writability. It does not: a `const` in `.rdata` is a variable and consumers read
it as one, so the rule keys on "not executable" instead. The constant was
documenting a decision that is no longer taken.1 parent f9ca398 commit bbf785e
2 files changed
Lines changed: 32 additions & 1 deletion
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
115 | 115 | | |
116 | 116 | | |
117 | 117 | | |
118 | | - | |
119 | 118 | | |
120 | 119 | | |
121 | 120 | | |
| |||
201 | 200 | | |
202 | 201 | | |
203 | 202 | | |
| 203 | + | |
| 204 | + | |
| 205 | + | |
| 206 | + | |
| 207 | + | |
| 208 | + | |
| 209 | + | |
| 210 | + | |
| 211 | + | |
| 212 | + | |
| 213 | + | |
| 214 | + | |
| 215 | + | |
| 216 | + | |
| 217 | + | |
| 218 | + | |
| 219 | + | |
204 | 220 | | |
205 | 221 | | |
206 | 222 | | |
| |||
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
214 | 214 | | |
215 | 215 | | |
216 | 216 | | |
| 217 | + | |
| 218 | + | |
| 219 | + | |
| 220 | + | |
| 221 | + | |
| 222 | + | |
| 223 | + | |
| 224 | + | |
| 225 | + | |
| 226 | + | |
| 227 | + | |
| 228 | + | |
| 229 | + | |
| 230 | + | |
| 231 | + | |
217 | 232 | | |
218 | 233 | | |
219 | 234 | | |
| |||
0 commit comments