diff options
author | Kartik K. Agaram <vc@akkartik.com> | 2015-11-04 23:44:46 -0800 |
---|---|---|
committer | Kartik K. Agaram <vc@akkartik.com> | 2015-11-04 23:44:46 -0800 |
commit | 436b2b2eac33b893f7b9b0a7229ac1d98c034d2c (patch) | |
tree | 6619f453b5fd99b204380b17b94e9d8321e642f1 /043new.cc | |
parent | 54275c64e2404612bf8754238bf71ae805f4022e (diff) | |
download | mu-436b2b2eac33b893f7b9b0a7229ac1d98c034d2c.tar.gz |
2360
More flailing around trying to come up with the right phase ordering. I've tried to narrow down each transform's constraints wrt transforms in previous layers. One issue that keeps biting me is the Type map containing empty records because of stray [] operations. That's gotta be important.
Diffstat (limited to '043new.cc')
-rw-r--r-- | 043new.cc | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/043new.cc b/043new.cc index 13240cfe..a851e3d5 100644 --- a/043new.cc +++ b/043new.cc @@ -49,7 +49,7 @@ case NEW: { } //:: translate 'new' to 'allocate' instructions that take a size instead of a type -:(after "Transform.push_back(check_instruction)" following "Transform.push_back(check_invalid_types)") // so that all types are defined +:(after "Transform.push_back(check_instruction)") // check_instruction will guard against direct 'allocate' instructions below Transform.push_back(transform_new_to_allocate); :(code) |