Please sign in to comment.
Don't mark functions that allocate and could result in GC as read only
These can have side effects if they cause an actual GC because of memory pressure. In that case it can also for example modify stack addresses because objects are forwarded. LLVM shouldn't remove those cases. The proper way to handle this would be to first do escape analysis and if it doesn't escape, we could switch to stack allocation. That stack allocation can then properly be seen as having no side effects.
- Loading branch information...
Showing with 0 additions and 3 deletions.