Note, I'm getting close to getting my part of the structure reorganization optimization minimally functional (my question about value range propagation remains open since I re-enabled a couple of optimizations to bypass it.) Therefore this is actually important for me to resolve.
I obviously generated calls to the standard library function "free." Also, similar calls to malloc didn't have that ".2" appended on them. I'd normally handle a problem like this with a Google search but "free.2" gets turned into "free to" and I get an insane number of junk search results. This is obviously an easy question to answer for those that have seen something similar in the past. Thanks, Gary Oblock CONFIDENTIALITY NOTICE: This e-mail message, including any attachments, is for the sole use of the intended recipient(s) and contains information that is confidential and proprietary to Ampere Computing or its subsidiaries. It is to be used solely for the purpose of furthering the parties' business relationship. Any review, copying, or distribution of this email (or any attachments thereto) is strictly prohibited. If you are not the intended recipient, please contact the sender immediately and permanently delete the original and any copies of this email and any attachments thereto.
