- User Since
- Feb 12 2020, 7:33 AM (42 w, 17 h)
Mon, Nov 30
Sun, Nov 29
I believe this happened becase when I removed the loop, I did not update MemorySSA. The exact error was from GVN, but this update seems to fix the stage 2 build compile time error locally (I checked by running the build bot script).
This introduced a compile-time error that showed up during a stage 2 build.
Mon, Nov 9
Fri, Nov 6
I'm so sorry, I saw that you fixed it, thank you.
I naively assumed that reverting it would be fine, I'm working on a fixing right now.
- Fixed failing test
Thu, Nov 5
removed non-parent revision.
using buildkite recommended fix
- Addressed nits
- Final Pre-commit testing
Wed, Nov 4
Tue, Nov 3
Hopefully the unrelated hwasan test failure is now fixed on master, trying again.
Nov 2 2020
ignore, testing pre-build bots again.
- Added triple to fix mangling errors in test
- Modified (unrelated) recently added test to have the mustprogress attribute
- Updated title, revision summary, and commit message
- Added documentation for struct and members
Nov 1 2020
Oct 30 2020
Oct 29 2020
Thank you for the comments. I think I follow, I'll post another less intrusive patch soon.
Oct 25 2020
- Adds test.
- Uses getExitBlocks() instead of getUniqueExitBlocks() and moved definition.
- Changed definition of hasNoExitBlocks() to use empty() instead of conditional
- Style changes in deleteDeadLoop for readibility.
Added word back in.
Add parent revision for buildkite.
Oct 21 2020
Oct 20 2020
Oct 19 2020
Sorry, I understand now. Is this more correct?
Oct 18 2020
Oct 16 2020
Reverted to prior diff.
Oct 14 2020
I think that phrase ("w/o maxobjsize deduction") could be a bit misleading, IINM, when @jdoerfert says w/o maxobjsize deduction he means without having the functionality built into the attributor to update the maximum object size estimate. So in the patch D87975, there's a crude over-approximation for the maxobjsize (getPointerMaxObjSize) and the numbers are for just using that over-approximation without including the changes in D87978 that refine it, so we would still need the maxobjsize attribute first in order to do this.
Oct 8 2020
Rebase to fix buildkite build.
Oct 7 2020
Updates made to try to remove infinite loops with no exit edge. It seems to work with the new pass manager, but hopelessly breaks for the old pass manager, changes planned.
Bump for bot.
Sep 30 2020
Updated to include syntax modifications in the llvm/utils
Fixed broken tests, think the changes make sense.
Fixed broken test.
Added a specific basic-aa maxobjsize test.
Sep 29 2020
Updated commit message.
Inliner changes now that the clang implementation in D86841 has changed. Can I remove the inliner nested loops and multiple loops tests now? They're not as relevant anymore.
Fixing buildkite build.
Removed extra file.
changed stats trackers