- User Since
- Jul 26 2017, 11:36 PM (81 w, 6 d)
Wed, Feb 13
I confirm this solves the issue.
Fri, Feb 1
Thanks Hans. I'll need you to do it on my behalf as I do not have commit privileges.
Jan 4 2019
Dec 30 2018
Dec 26 2018
Dec 23 2018
I think this patch broke Zig's tests:
Dec 4 2018
Added Rui's test case. Thank you for helping me with that. Please note that I do not have commit privileges and so someone will have to merge this on my behalf.
Aug 27 2018
Aug 25 2018
Addressed review feedback
Aug 22 2018
Jul 26 2018
Thanks. Can you do the commit? I do not have commit access.
Jul 9 2018
Jun 15 2018
Ping. Is it time yet? Looks like the stated blockers are resolved now.
Apr 11 2018
I confirm that this fixes https://bugs.llvm.org/show_bug.cgi?id=36991
Mar 30 2018
Mar 2 2018
Would llvm interact with grow_memory or memory_size instructions? Seems like that would be the frontend or standard library's job. It's not in LLVM's business to interact with the "OS" by allocating memory.
Is there anything stopping this from landing in svn?
Feb 19 2018
Never mind these changes. I've redesigned how coroutines will work in Zig and they no longer depend on these changes.
Feb 15 2018
Feb 12 2018
Jan 16 2018
Hans, thank you for reviewing. I do not have commit access; would you mind committing it for me, in whatever order you prefer?
Jan 11 2018
Jan 9 2018
Jan 8 2018
I would have selected a repository but the instructions explicitly say not to:
Leave the Repository field blank.
Jan 6 2018
I'll be careful next time, thanks. I used the web interface. Arcanist seemed more involved, but if that is preferable I can do it next time.
Thank you, I will CC llvm-commits next time. I followed these instructions: https://llvm.org/docs/Phabricator.html
I would also like to request that this is backported to the release_60 branch.
Nov 2 2017
Which we prefer, maximum IO performance or a reliable error handling?
Oct 23 2017
Aug 18 2017
- Can we have this even without tests?
- Can we have this in 5.0.0?