about summary refs log tree commit diff stats
path: root/apps/mulisp.subx
diff options
context:
space:
mode:
authorKartik Agaram <vc@akkartik.com>2020-10-06 00:36:28 -0700
committerKartik Agaram <vc@akkartik.com>2020-10-06 00:36:28 -0700
commitce094a5d827b82c48eb76b1b4c04cf899219c33b (patch)
tree5fe3a3ef14e3d7de3b291273378935500393ea80 /apps/mulisp.subx
parente41bc160a0dfee0c38ecf20b20ddaf7e6f3da408 (diff)
downloadmu-ce094a5d827b82c48eb76b1b4c04cf899219c33b.tar.gz
6968
Snapshot that requires a check in the Mu compiler.

Currently I don't spill a register if it could possibly be over-written
by a function output within. However, find-in-call-path is a good example
of where this constraint is too lenient and results in unsafe code. The
variable `curr` gets clobbered during loop update by the variable `match?`.

What's the answer? Perhaps we should ban all conditional updates to function
outputs? That'd be dashed inconvenient.
Diffstat (limited to 'apps/mulisp.subx')
0 files changed, 0 insertions, 0 deletions
0 111 112 113 114 115 116 117 118 119 120 121 122 123 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 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270