modocache (Brian Gesiak)
User

Projects

User does not belong to any projects.

User Details

User Since
Feb 16 2014, 1:10 AM (230 w, 4 d)

Recent Activity

Sat, Jul 14

modocache committed rC337103: Add caching when looking up coroutine_traits.
Add caching when looking up coroutine_traits
Sat, Jul 14, 11:27 AM
modocache committed rL337103: Add caching when looking up coroutine_traits.
Add caching when looking up coroutine_traits
Sat, Jul 14, 11:27 AM
modocache closed D48981: Add caching when looking up coroutine_traits.
Sat, Jul 14, 11:26 AM
modocache accepted D48981: Add caching when looking up coroutine_traits.

Yup, LGTM! I'll land this now.

Sat, Jul 14, 11:04 AM

Tue, Jul 10

modocache committed rC336750: [SemaCXX] Remove comment from coroutines test, NFC.
[SemaCXX] Remove comment from coroutines test, NFC
Tue, Jul 10, 6:06 PM
modocache committed rL336750: [SemaCXX] Remove comment from coroutines test, NFC.
[SemaCXX] Remove comment from coroutines test, NFC
Tue, Jul 10, 6:05 PM
modocache committed rL336748: Remove qualtype qualifier in coroutine error to prevent assert in debug.
Remove qualtype qualifier in coroutine error to prevent assert in debug
Tue, Jul 10, 5:51 PM
modocache committed rC336748: Remove qualtype qualifier in coroutine error to prevent assert in debug.
Remove qualtype qualifier in coroutine error to prevent assert in debug
Tue, Jul 10, 5:51 PM
modocache closed D49099: Remove qualtype qualifier in coroutine error to prevent assert in debug.
Tue, Jul 10, 5:50 PM
modocache added a comment to D49099: Remove qualtype qualifier in coroutine error to prevent assert in debug.

If you don't have commit access, let me know here if you'd like me to commit this on your behalf.

Tue, Jul 10, 6:31 AM
modocache accepted D49099: Remove qualtype qualifier in coroutine error to prevent assert in debug.

Excellent, thanks!

Tue, Jul 10, 6:18 AM

Thu, Jul 5

modocache resigned from D48981: Add caching when looking up coroutine_traits.

This LGTM but I'll just wait for @GorNishanov to accept the patch, just in case I'm missing something. I'd be happy to commit this for you once Gor accepts! :)

Thu, Jul 5, 11:07 AM

Tue, Jul 3

modocache added inline comments to D48863: [Sema] Explain coroutine_traits template in diag.
Tue, Jul 3, 4:13 PM
modocache updated the diff for D48863: [Sema] Explain coroutine_traits template in diag.

Oops, apologies, I included a line I shouldn't have in the previous diff.

Tue, Jul 3, 12:29 PM

Mon, Jul 2

modocache created D48863: [Sema] Explain coroutine_traits template in diag.
Mon, Jul 2, 8:25 PM

Tue, Jun 26

modocache committed rC335655: [AST] Fix typo in LazyOffsetPtr::get docs (NFC).
[AST] Fix typo in LazyOffsetPtr::get docs (NFC)
Tue, Jun 26, 1:10 PM
modocache committed rL335655: [AST] Fix typo in LazyOffsetPtr::get docs (NFC).
[AST] Fix typo in LazyOffsetPtr::get docs (NFC)
Tue, Jun 26, 1:10 PM

Sat, Jun 23

modocache committed rL335422: [Coroutines] Less IR for noexcept await_resume.
[Coroutines] Less IR for noexcept await_resume
Sat, Jun 23, 12:02 PM
modocache committed rC335422: [Coroutines] Less IR for noexcept await_resume.
[Coroutines] Less IR for noexcept await_resume
Sat, Jun 23, 12:02 PM
modocache closed D47673: [Coroutines] Less IR for noexcept await_resume.
Sat, Jun 23, 12:02 PM
modocache closed D47673: [Coroutines] Less IR for noexcept await_resume.
Sat, Jun 23, 12:02 PM
modocache updated the diff for D47673: [Coroutines] Less IR for noexcept await_resume.

Great, thanks @GorNishanov! I moved the 'can throw' logic into a function called 'memberCallExpressionCanThrow', to convey that some dyn_cast'ing is going on.

Sat, Jun 23, 11:39 AM
modocache committed rL335420: [Sema] isValidCoroutineContext FIXME and citations.
[Sema] isValidCoroutineContext FIXME and citations
Sat, Jun 23, 11:05 AM
modocache committed rC335420: [Sema] isValidCoroutineContext FIXME and citations.
[Sema] isValidCoroutineContext FIXME and citations
Sat, Jun 23, 11:05 AM
modocache closed D48519: [Sema] isValidCoroutineContext FIXME and citations.
Sat, Jun 23, 11:05 AM
modocache updated the diff for D48519: [Sema] isValidCoroutineContext FIXME and citations.

Great, thanks for the review! I added a reference to N4499.

Sat, Jun 23, 10:32 AM
modocache added inline comments to D48519: [Sema] isValidCoroutineContext FIXME and citations.
Sat, Jun 23, 8:49 AM
modocache added a comment to D48519: [Sema] isValidCoroutineContext FIXME and citations.

Also @GorNishanov I'm curious about your two cents on whether comments like these are valuable. If you think they are I may add a few more with post-commit review.

Sat, Jun 23, 8:47 AM
modocache created D48519: [Sema] isValidCoroutineContext FIXME and citations.
Sat, Jun 23, 8:46 AM

Jun 13 2018

modocache committed rL334641: [Darwin] Do not error on '-lto_library' option.
[Darwin] Do not error on '-lto_library' option
Jun 13 2018, 12:05 PM
modocache committed rLLD334641: [Darwin] Do not error on '-lto_library' option.
[Darwin] Do not error on '-lto_library' option
Jun 13 2018, 12:04 PM
modocache closed D47994: [Darwin] Do not error on '-lto_library' option.
Jun 13 2018, 12:04 PM
modocache added a comment to D47994: [Darwin] Do not error on '-lto_library' option.

Great! Thanks for the review :)

Jun 13 2018, 12:04 PM
modocache added a comment to D47994: [Darwin] Do not error on '-lto_library' option.

Friendly ping! Is this alright by you, @smeenai and @pcc?

Jun 13 2018, 7:34 AM

Jun 12 2018

modocache added a comment to rL334507: Fix -DBUILD_SHARED_LIBS=1 build.

Great, thank you!

Jun 12 2018, 10:53 AM
modocache accepted D48073: [MachO] Add lldCommon to LINK_LIBS.

Thanks for catching this! LGTM.

Jun 12 2018, 4:42 AM

Jun 11 2018

modocache updated the diff for D47994: [Darwin] Do not error on '-lto_library' option.

Thanks for the reviews! I adopted @pcc's suggestion to ignore the option without printing a warning. (I also considered calling llvm::opt::Arg::claim, but it looks like no other arguments are claimed, and lld doesn't print warnings for unclaimed arguments anyway.) I updated the help text and the test as well.

Jun 11 2018, 8:23 PM
modocache committed rL334466: [Darwin] Use errorHandler from liblldCommon.
[Darwin] Use errorHandler from liblldCommon
Jun 11 2018, 7:38 PM
modocache committed rLLD334466: [Darwin] Use errorHandler from liblldCommon.
[Darwin] Use errorHandler from liblldCommon
Jun 11 2018, 7:38 PM
modocache closed D47998: [Darwin] Use errorHandler from liblldCommon.
Jun 11 2018, 7:38 PM
modocache updated the diff for D47998: [Darwin] Use errorHandler from liblldCommon.

Thanks for the reviews! I'm updating this so that it no longer includes the warning I added in D47994. I'll commit in in a second.

Jun 11 2018, 7:08 PM
modocache updated the diff for D47998: [Darwin] Use errorHandler from liblldCommon.

Oops! I fixed a typo in the error limit exceeded message.

Jun 11 2018, 8:13 AM

Jun 10 2018

modocache created D47998: [Darwin] Use errorHandler from liblldCommon.
Jun 10 2018, 7:05 PM
modocache created D47994: [Darwin] Do not error on '-lto_library' option.
Jun 10 2018, 11:34 AM

Jun 3 2018

modocache updated subscribers of D47673: [Coroutines] Less IR for noexcept await_resume.
Jun 3 2018, 8:44 AM

Jun 2 2018

modocache created D47673: [Coroutines] Less IR for noexcept await_resume.
Jun 2 2018, 12:18 AM

May 28 2018

modocache accepted D47454: [coroutines] Pass implicit object parameter to promise ctor (fix BUG37604).

Great! Thanks @GorNishanov!

May 28 2018, 11:09 AM

May 22 2018

modocache updated the diff for D46628: [ELF] Add --strip-debug-non-line option.

Thanks again for the reviews. I removed the extraneous else, and reverted the string switch back to what I had originally.

May 22 2018, 8:38 PM
modocache added a comment to D46628: [ELF] Add --strip-debug-non-line option.

Does gold really preserve .debug_info and .debug_abbrev? Generally .debug_info is by far the largest DWARF section and so the one you most likely want to remove.

May 22 2018, 8:09 PM
modocache added a comment to D46628: [ELF] Add --strip-debug-non-line option.

Sorry for letting this languish a bit. I took some time to experiment. Long story short I think llvm-dwarfdump and lldb aren't able to verify this option at the moment.

May 22 2018, 6:36 PM

May 21 2018

modocache committed rL332878: [DebugInfo] Fix typo "DWARG" in test comment (NFC).
[DebugInfo] Fix typo "DWARG" in test comment (NFC)
May 21 2018, 12:52 PM

May 19 2018

modocache committed rL332812: Re-revert "[Option] Fix PR37006 prefix choice in findNearest".
Re-revert "[Option] Fix PR37006 prefix choice in findNearest"
May 19 2018, 9:25 AM
modocache added a comment to rC332804: [Driver] Loosen test for LLVM findNearest.

Yes, unfortunately I haven’t been able to reproduce this locally, on any build environment I have access to. There’s a discussion about this in https://reviews.llvm.org/D46776, but I can’t figure out why the buildbots wouldn’t behave the same way. Passing ‘-triple x86_64-scei-ps4-ubuntu’ as suggested there doesn’t make a difference for me locally. And indeed the argument parsing occurs before the triple is taken into account anyway, so it makes sense to me that it wouldn’t make a difference.

May 19 2018, 5:57 AM
modocache committed rL332806: [Driver] Temporarily remove test for LLVM findNearest.
[Driver] Temporarily remove test for LLVM findNearest
May 19 2018, 5:47 AM
modocache committed rC332806: [Driver] Temporarily remove test for LLVM findNearest.
[Driver] Temporarily remove test for LLVM findNearest
May 19 2018, 5:47 AM
modocache committed rL332805: Un-revert "[Option] Fix PR37006 prefix choice in findNearest".
Un-revert "[Option] Fix PR37006 prefix choice in findNearest"
May 19 2018, 5:07 AM
modocache committed rC332804: [Driver] Loosen test for LLVM findNearest.
[Driver] Loosen test for LLVM findNearest
May 19 2018, 4:51 AM
modocache committed rL332804: [Driver] Loosen test for LLVM findNearest.
[Driver] Loosen test for LLVM findNearest
May 19 2018, 4:51 AM

May 15 2018

modocache added a comment to D46776: [Option] Fix PR37006 prefix choice in findNearest.

Hmm... but the >1 condition is such that an edit distance of greater than 1 results in no suggestion, whereas an edit distance of 1 or 0 results in a suggestion. In this case -- and apparently only on certain platforms' buildbots -- the edit distance between -debug-info-macros and -debug-info-macro is 1, and so it should display a suggestion.

May 15 2018, 2:29 PM

May 14 2018

modocache added a comment to D46776: [Option] Fix PR37006 prefix choice in findNearest.

I'm not yet sure why, but this change caused buildbot failures due to a test in Clang for the "did you mean" feature (example: http://lab.llvm.org:8011/builders/llvm-clang-lld-x86_64-scei-ps4-ubuntu-fast/builds/29988). I couldn't figure out why the buildbots would fail whereas the Clang tests pass for me locally, and so reverted this change for the time being, in rL332304. I'll try to resubmit once I've figured out and fixed the issue.

May 14 2018, 3:43 PM
modocache committed rL332304: Revert "[Option] Fix PR37006 prefix choice in findNearest".
Revert "[Option] Fix PR37006 prefix choice in findNearest"
May 14 2018, 3:40 PM
modocache added a comment to D46776: [Option] Fix PR37006 prefix choice in findNearest.

Thanks for the reviews, and for pointing out the bug!

May 14 2018, 2:40 PM
modocache committed rL332299: [Option] Fix PR37006 prefix choice in findNearest.
[Option] Fix PR37006 prefix choice in findNearest
May 14 2018, 2:38 PM
modocache closed D46776: [Option] Fix PR37006 prefix choice in findNearest.
May 14 2018, 2:38 PM
modocache added inline comments to D46776: [Option] Fix PR37006 prefix choice in findNearest.
May 14 2018, 9:36 AM

May 11 2018

modocache created D46776: [Option] Fix PR37006 prefix choice in findNearest.
May 11 2018, 2:37 PM

May 10 2018

modocache added a comment to D43242: [Coroutines] PR34897: Fix incorrect elisions.

Hooray! Thanks again for the review, @GorNishanov.

May 10 2018, 8:26 PM
modocache committed rL332077: [Coroutines] PR34897: Fix incorrect elisions.
[Coroutines] PR34897: Fix incorrect elisions
May 10 2018, 8:16 PM
modocache closed D43242: [Coroutines] PR34897: Fix incorrect elisions.
May 10 2018, 8:16 PM
modocache committed rL332075: [Support] Add docs for 'openFileFor{Write,Read}'.
[Support] Add docs for 'openFileFor{Write,Read}'
May 10 2018, 6:51 PM
modocache closed D46499: [Support] Add docs for 'openFileFor{Write,Read}'.
May 10 2018, 6:51 PM
modocache updated the diff for D46499: [Support] Add docs for 'openFileFor{Write,Read}'.

I updated this diff to not only document how the ResultFD is set, but also make it a little more consistent across platforms. Previously Windows would only sometimes set it to -1 in the case of failure, now it always does.

May 10 2018, 2:17 PM
modocache added a comment to D46628: [ELF] Add --strip-debug-non-line option.

Please just bring back the first patch to line 1316 and submit. Thanks!

May 10 2018, 11:39 AM
modocache added a comment to D46628: [ELF] Add --strip-debug-non-line option.

Thanks for all the review!

May 10 2018, 10:21 AM

May 9 2018

modocache updated the diff for D46628: [ELF] Add --strip-debug-non-line option.

Thanks for the review! I adopted the changes you suggested. As for validating the debug info, what about using 'llvm-dwarfdump -verify'? In fact running that on the output of this new option resulted in errors, so I'll address those.

May 9 2018, 10:04 PM
modocache added a comment to D46499: [Support] Add docs for 'openFileFor{Write,Read}'.

Correct! I'll mention that as well.

May 9 2018, 8:58 AM
modocache added a comment to D46499: [Support] Add docs for 'openFileFor{Write,Read}'.

Thanks for the comments!

May 9 2018, 8:55 AM

May 8 2018

modocache created D46628: [ELF] Add --strip-debug-non-line option.
May 8 2018, 10:16 PM

May 7 2018

modocache updated the diff for D43242: [Coroutines] PR34897: Fix incorrect elisions.

Sorry it took me a while to get around to this, but I think this new approach fits more along the lines of what you were thinking, @GorNishanov. I also confirmed that it optimizes the program you linked to just as well as before.

May 7 2018, 9:46 AM

May 5 2018

modocache created D46499: [Support] Add docs for 'openFileFor{Write,Read}'.
May 5 2018, 9:11 PM

May 4 2018

modocache added a comment to D45860: [Coroutines] Catch exceptions in await_resume.

Thanks again for all the reviews, @GorNishanov! Very much appreciated.

May 4 2018, 7:09 AM
modocache committed rL331519: [Coroutines] Catch exceptions in await_resume.
[Coroutines] Catch exceptions in await_resume
May 4 2018, 7:08 AM
modocache committed rC331519: [Coroutines] Catch exceptions in await_resume.
[Coroutines] Catch exceptions in await_resume
May 4 2018, 7:07 AM
modocache closed D45860: [Coroutines] Catch exceptions in await_resume.
May 4 2018, 7:07 AM

May 2 2018

modocache updated the diff for D45860: [Coroutines] Catch exceptions in await_resume.

Oops, thanks for testing on release mode, @GorNishanov. Turns out I had a dangling pointer. With this update the tests pass on both release and debug.

May 2 2018, 6:06 PM
modocache updated the diff for D45860: [Coroutines] Catch exceptions in await_resume.

Thanks for the review, @GorNishanov. Here's a more correct solution: an i1 is used to keep track of whether await_resume threw. If it did, the coroutine body is skipped, and we go straight to the final suspend point. Otherwise, the coroutine body is executed as normal.

May 2 2018, 11:24 AM

Apr 21 2018

modocache committed rL330530: Add tests for llvm-bcanalyzer stream types.
Add tests for llvm-bcanalyzer stream types
Apr 21 2018, 5:08 PM
modocache committed rC330530: Add tests for llvm-bcanalyzer stream types.
Add tests for llvm-bcanalyzer stream types
Apr 21 2018, 5:07 PM
modocache closed D41980: Add tests for llvm-bcanalyzer stream types.
Apr 21 2018, 5:07 PM
modocache added a comment to D41979: [bcanalyzer] Recognize more stream types.

Strange, the revision appeared to have been "Accepted" by @JDevlieghere. I wonder why the message says it wasn't accepted...? Apologies in advance if I did something incorrectly when landing this.

Apr 21 2018, 5:00 PM
modocache committed rL330529: [bcanalyzer] Recognize more stream types.
[bcanalyzer] Recognize more stream types
Apr 21 2018, 4:56 PM
This revision was not accepted when it landed; it landed in state Needs Review.
Apr 21 2018, 4:56 PM
modocache updated the diff for D41979: [bcanalyzer] Recognize more stream types.

Thanks, @JDevlieghere! I added two tests like the ones you described. Thankfully it doesn't crash because llvm-bcanalyzer verifies the bitcode invariant that input sizes be a multiple of 4.

Apr 21 2018, 4:35 PM
modocache added a dependency for D41980: Add tests for llvm-bcanalyzer stream types: D41979: [bcanalyzer] Recognize more stream types.
Apr 21 2018, 10:12 AM
modocache added a dependent revision for D41979: [bcanalyzer] Recognize more stream types: D41980: Add tests for llvm-bcanalyzer stream types.
Apr 21 2018, 10:12 AM
modocache updated the diff for D41980: Add tests for llvm-bcanalyzer stream types.

Added -fmodule-format=raw.

Apr 21 2018, 10:11 AM
modocache updated the diff for D41979: [bcanalyzer] Recognize more stream types.

Sorry for letting this diff languish for so long. I updated the tests to be simple files with just the bytes necessary to be picked up as a specific stream type. I also moved the magic number reading over to a static helper function. I considered adding this function as a member of llvm::BirstreamReader, but chose not to for now, because doing so (as far as I can tell) would mean encoding Clang's magic numbers into LLVM's machinery. Let me know if you have different thoughts. Thanks!

Apr 21 2018, 9:50 AM

Apr 19 2018

modocache created D45860: [Coroutines] Catch exceptions in await_resume.
Apr 19 2018, 8:25 PM

Apr 12 2018

modocache committed rL329957: Let llvm-diff correctly deal with….
Let llvm-diff correctly deal with…
Apr 12 2018, 2:33 PM
modocache closed D34856: Let llvm-diff correctly deal with Undef/ConstantAggregateZero/ConstantVector/IndirectBr.
Apr 12 2018, 2:32 PM