Page MenuHomePhabricator

vsk (Vedant Kumar)
User

Projects

User Details

User Since
Jul 8 2015, 10:26 AM (193 w, 1 d)

Recent Activity

Mon, Mar 18

vsk added a comment to D59417: [GVN] Add default debug location when constructing PHI nodes.
In D59417#1431369, @vsk wrote:

As for instructions at the start of the block - I'm pretty sure that a while back @probinson made a change to ensure that cascade locations couldn't occur at the start of a block (that we'd set to line zero down in the AsmPrinter/DwarfDebug if that occurred) so we shouldn't end up with super weird/layout-based cascade locations for instructions generated from phis at the start of blocks.

That makes sense. What if a block has multiple phis? I.e. if the first phi in a block has a location but the second phi doesn't, is that a bug, or do we expect the location to cascade?

Locations cascade, with one exception: If the first instruction after a label does not have an explicit source location, we emit line 0.

Mon, Mar 18, 10:42 AM · Restricted Project

Fri, Mar 15

vsk added a comment to D59417: [GVN] Add default debug location when constructing PHI nodes.
Phis often cannot assume a previous location (say, if they're at the start of a block).

Not sure I follow this bit - setting a zero location doesn't make them any easier to debug, does it? Or was it that the "cascade location" (whatever the previous instruction was) the source of confusion?

Fri, Mar 15, 1:16 PM · Restricted Project
vsk added a comment to D59417: [GVN] Add default debug location when constructing PHI nodes.

I believe this is a patch to fix PR37964?

Hrm - if debugify diagnoses all instances of instructions without locations as buggy, that sounds very noisy to me. How does it handle all the other cases of merged locations that end up with no location? (if my recollection is accurate and the code is still doing this - merged locations that aren't the same and that aren't calls get no location, not a zero location)

Fri, Mar 15, 11:31 AM · Restricted Project

Thu, Mar 14

vsk accepted D59277: Speeding up llvm-cov export with multithreaded renderFiles implementation..

Thanks, lgtm.

Thu, Mar 14, 9:12 AM · Restricted Project

Wed, Mar 13

vsk added a comment to D59277: Speeding up llvm-cov export with multithreaded renderFiles implementation..

Thanks for working on this!

Wed, Mar 13, 4:40 PM · Restricted Project
vsk added inline comments to D59277: Speeding up llvm-cov export with multithreaded renderFiles implementation..
Wed, Mar 13, 10:40 AM · Restricted Project
vsk added a reviewer for D59288: [DebugInfoMetadata] Move main subprogram DIFlag into DISPFlags: steven_wu.

+ Steven, is debug info bitcode backwards compatibility important for the App Store? (I’m not 100% sure, but I think it is, in which case we’d need to 1) detect old DI metadata and 2) auto upgrade it?)

Wed, Mar 13, 8:14 AM · Restricted Project

Mon, Mar 11

vsk accepted D59206: [SimplifyCFG] Retain debug info when threading jumps with critical edges.

Thanks, looks great (and thanks to @gbedwell for finding this)!

Mon, Mar 11, 8:58 AM · Restricted Project

Fri, Mar 8

vsk accepted D58963: [JumpThreading] Retain debug info when replacing branch instructions.

Thanks, lgtm as well.

Fri, Mar 8, 11:45 AM · Restricted Project

Fri, Mar 1

vsk added a comment to D58726: [DebugInfo][Docs] Explicitly document how dbg.value intrinsics are interpreted in optimized code.

+1, thanks for codifying all of this!

Fri, Mar 1, 4:32 PM · Restricted Project

Thu, Feb 28

vsk added a comment to D58737: [InstrProf] Use separate comdat group for data and counters.
In D58737#1412846, @rnk wrote:

Oops, forgot to respond to this...

In D58737#1412734, @vsk wrote:

I'm confused by this wording re: comdats in the LangRef: "All global objects that specify this key will only end up in the final object file if the linker chooses that key over some other key". Why can multiple global objects with the same comdat key end up in the final object file?

These words are trying to say that, some number of global objects can use a comdat key. If the object file they are contained in has the prevailing definition of that comdat key, then they will be included, and they will be discarded if not. The prevailing object is typically just the first object file that uses the comdat.

So, multiple objects from *one TU* can use the key and end up in the final binary, but objects from different TUs will never end up mixed together in the final binary.

Thu, Feb 28, 10:38 AM · Restricted Project, Restricted Project, Restricted Project

Wed, Feb 27

vsk added a comment to D58737: [InstrProf] Use separate comdat group for data and counters.

I'm confused by this wording re: comdats in the LangRef: "All global objects that specify this key will only end up in the final object file if the linker chooses that key over some other key". Why can multiple global objects with the same comdat key end up in the final object file?

Wed, Feb 27, 2:40 PM · Restricted Project, Restricted Project, Restricted Project

Tue, Feb 26

vsk committed rG73522d167890: [HotColdSplit] Disable splitting for sanitized functions (authored by vsk).
[HotColdSplit] Disable splitting for sanitized functions
Tue, Feb 26, 2:55 PM
vsk accepted D58691: [MS] Don't emit coverage for deleting dtors.

Thanks! Lgtm.

Tue, Feb 26, 12:11 PM · Restricted Project, Restricted Project
vsk added inline comments to D58691: [MS] Don't emit coverage for deleting dtors.
Tue, Feb 26, 11:39 AM · Restricted Project, Restricted Project

Mon, Feb 25

vsk accepted D58661: [llvm-cov] Fix llvm-cov on Windows and un-XFAIL test.
Mon, Feb 25, 6:14 PM · Restricted Project, Restricted Project
vsk added a comment to D58661: [llvm-cov] Fix llvm-cov on Windows and un-XFAIL test.

I suppose Names{Start,End} are needed on Windows so that we can find section boundaries.

Mon, Feb 25, 6:14 PM · Restricted Project, Restricted Project

Thu, Feb 21

vsk added inline comments to D58044: [DwarfDebug] Dump call site debug info into DWARF.
Thu, Feb 21, 11:46 AM · debug-info
vsk added inline comments to D58044: [DwarfDebug] Dump call site debug info into DWARF.
Thu, Feb 21, 11:26 AM · debug-info
vsk accepted D34499: Expose __gcov_flush for parity with libgcov in the gcc project.

Thanks, LGTM. If you don't have commit access, let me know and I can land this on your behalf.

Thu, Feb 21, 11:21 AM · Restricted Project, Restricted Project
vsk added reviewers for D58035: [clang/DIVar] Emit flag for params that have unchanged values: bricci, rsmith.

+ rsmith, + bricci for review.

Thu, Feb 21, 11:02 AM · debug-info

Wed, Feb 20

vsk added inline comments to D34499: Expose __gcov_flush for parity with libgcov in the gcc project.
Wed, Feb 20, 11:14 AM · Restricted Project, Restricted Project

Feb 19 2019

vsk committed rGa0b972547978: [llvm-cov] Add support for gcov --hash-filenames option (authored by vsk).
[llvm-cov] Add support for gcov --hash-filenames option
Feb 19 2019, 12:45 PM
vsk accepted D58370: [llvm-cov] Add support for gcov --hash-filenames option..

Hi @iignatev, thanks for the patch. LGTM.

Feb 19 2019, 10:49 AM · Restricted Project

Feb 15 2019

vsk committed rG5f5cac3ae29d: [CodeExtractor] Do not lift lifetime.end markers for region inputs (authored by vsk).
[CodeExtractor] Do not lift lifetime.end markers for region inputs
Feb 15 2019, 10:47 AM
vsk committed rG47a0c9b69cd7: [HotColdSplit] Schedule splitting late to fix perf regression (authored by vsk).
[HotColdSplit] Schedule splitting late to fix perf regression
Feb 15 2019, 10:47 AM

Feb 14 2019

vsk updated the diff for D58258: [HotColdSplit] Schedule splitting late to fix perf regression.
  • Add a NewPM LTO pre-link test.
  • Schedule splitting at the same point in the old & new PM's.
Feb 14 2019, 5:24 PM · Restricted Project
vsk updated subscribers of D58258: [HotColdSplit] Schedule splitting late to fix perf regression.
Feb 14 2019, 4:47 PM · Restricted Project
vsk added a comment to D57805: [HotColdSplit] Move splitting after instrumented PGO use.

... I will try moving the splitting to after the ThinLTO backend (post-thinlink) inlining and see what effect there is. Theoretically we should be getting more accurate importing/inlining, it would be good to understand where this is going wrong if not!

Feb 14 2019, 3:37 PM · Restricted Project
vsk accepted D58259: Fixed failure on Darwin due to r354064.

Thanks, lgtm.

Feb 14 2019, 3:36 PM · Restricted Project
vsk created D58258: [HotColdSplit] Schedule splitting late to fix perf regression.
Feb 14 2019, 3:27 PM · Restricted Project
vsk created D58253: [CodeExtractor] Do not lift lifetime.end markers for region inputs.
Feb 14 2019, 2:07 PM · Restricted Project
vsk added a comment to D57834: [CodeExtractor] Only lift lifetime markers present in the extraction region.

In this example there are two possible entry points in region, so it can't be extracted (first block in region should dominate the others). Maybe there are better examples of issue?

Feb 14 2019, 2:07 PM · Restricted Project
vsk updated subscribers of D57986: [ProfileData] Sort FuncData before iteration to remove non-determinism.

I think this could roughly double the memory utilization of the writer, which might be problematic because the number of records to write can be high. (@dblaikie did some work on reducing memory usage in this area, he might have hard data about this.)

Feb 14 2019, 10:46 AM · Restricted Project, Restricted Project

Feb 13 2019

vsk added a comment to D57834: [CodeExtractor] Only lift lifetime markers present in the extraction region.

@kachkov98 @davidxl apologies, but this patch is still not correct.

Feb 13 2019, 6:20 PM · Restricted Project
vsk accepted D58156: [Sanitizer] On Darwin `__sanitizer_print_stack_trace` only prints topmost frame.

Thanks, LGTM. Could you wait for another +1? It's been a while since I've looked at this code, and I think another review would help make sure this is safe.

Feb 13 2019, 1:08 PM · Restricted Project, Restricted Project
vsk committed rG4b0cc9a7c80f: [CodeExtractor] Only lift lifetime markers present in the extraction region (authored by vsk).
[CodeExtractor] Only lift lifetime markers present in the extraction region
Feb 13 2019, 11:56 AM

Feb 11 2019

vsk accepted D58071: Fix auto-upgrade for the new parameter to llvm.objectsize.

Thanks, lgtm. Steven?

Feb 11 2019, 1:18 PM · Restricted Project
vsk added a comment to D57805: [HotColdSplit] Move splitting after instrumented PGO use.
In D57805#1393416, @vsk wrote:

@tejohnson have you had a chance to evaluate performance with IR-PGO + splitting enabled?

I have one data point, more below.

Our internal CI shows performance regressions on SPEC/CINT2000 with FE-PGO + splitting enabled. Allowing inlining of split functions reduces the perf regression,

This is controlled by the MinSize attribute, right?

Feb 11 2019, 12:37 PM · Restricted Project
vsk added a comment to D57265: [PM/CC1] Add -f[no-]split-cold-code CC1 options to toggle splitting.

I'd prefer not adding this kind of state to PassBuilder. SplitColdCode is soemthing that refers to the construction of one particular pipeline, not to pipeline-building in general. It should be an argument passed down through the build*Pipeline calls.

Feb 11 2019, 11:41 AM · Restricted Project
vsk added a comment to D57805: [HotColdSplit] Move splitting after instrumented PGO use.

@tejohnson have you had a chance to evaluate performance with IR-PGO + splitting enabled?

Feb 11 2019, 11:13 AM · Restricted Project

Feb 8 2019

vsk retitled D57985: [test-suite] Add cmake option to use IR PGO (TEST_SUITE_USE_IR_PGO) from Add cmake option to use IR PGO (TEST_SUITE_USE_IR_PGO) to [test-suite] Add cmake option to use IR PGO (TEST_SUITE_USE_IR_PGO).
Feb 8 2019, 4:17 PM · Restricted Project
vsk created D57985: [test-suite] Add cmake option to use IR PGO (TEST_SUITE_USE_IR_PGO).
Feb 8 2019, 4:17 PM · Restricted Project
Herald added a project to D56761: Add a parameter to the objectsize intrinsic that controls whether to evaluate size dynamically: Restricted Project.

I think this breaks bitcode backwards compatibility:

Feb 8 2019, 1:21 PM · Restricted Project
vsk committed rG0e5dd512aae0: [CodeExtractor] Restore outputs after creating exit stubs (authored by vsk).
[CodeExtractor] Restore outputs after creating exit stubs
Feb 8 2019, 12:50 PM
vsk accepted D57957: [NFC] Avoid passing blocks vector to the OutlineRegionInfo constructor by value..

Thanks, lgtm.

Feb 8 2019, 12:08 PM · Restricted Project
vsk accepted D57919: [CodeExtractor] Restore outputs after creating exit stubs.

Thanks for doing this! LGTM with a simple change.

Feb 8 2019, 10:56 AM · Restricted Project
vsk added inline comments to D57957: [NFC] Avoid passing blocks vector to the OutlineRegionInfo constructor by value..
Feb 8 2019, 10:03 AM · Restricted Project
vsk added reviewers for D57957: [NFC] Avoid passing blocks vector to the OutlineRegionInfo constructor by value.: fhahn, davidxl.
Feb 8 2019, 10:03 AM · Restricted Project

Feb 7 2019

vsk added a comment to D57919: [CodeExtractor] Restore outputs after creating exit stubs.

Thanks! This mostly looks good, and I believe it resolves llvm.org/PR40455.

Feb 7 2019, 12:06 PM · Restricted Project
vsk accepted D57900: [HotColdSplit] With PGO add profile entry metadata to split cold function.

Thanks, lgtm.

Feb 7 2019, 9:48 AM · Restricted Project

Feb 6 2019

vsk accepted D57215: [CodeExtractor] Update function's assumption cache after extracting blocks from it.

LGTM, but, please wait for a +1 from someone more familiar with AssumptionCache before committing.

Feb 6 2019, 3:30 PM · Restricted Project
vsk updated the diff for D57265: [PM/CC1] Add -f[no-]split-cold-code CC1 options to toggle splitting.

Rebase.

Feb 6 2019, 2:16 PM · Restricted Project
vsk added reviewers for D57265: [PM/CC1] Add -f[no-]split-cold-code CC1 options to toggle splitting: fedor.sergeev, philip.pfaffe.

Thanks @hiraditya. I'd also like to get a +1 from someone who's worked on the NewPM infrastructure extensively, just to make sure those changes look ok.

Feb 6 2019, 2:09 PM · Restricted Project
vsk added a comment to D57215: [CodeExtractor] Update function's assumption cache after extracting blocks from it.

@sdmitriev thanks for the patch!

Feb 6 2019, 2:04 PM · Restricted Project
vsk created D57834: [CodeExtractor] Only lift lifetime markers present in the extraction region.
Feb 6 2019, 11:39 AM · Restricted Project

Feb 5 2019

vsk accepted D57805: [HotColdSplit] Move splitting after instrumented PGO use.

Thanks, LGTM.

Feb 5 2019, 8:26 PM · Restricted Project
vsk committed rGbd94b4287c9e: [HotColdSplit] Do not split out `resume` instructions (authored by vsk).
[HotColdSplit] Do not split out `resume` instructions
Feb 5 2019, 3:39 PM

Feb 4 2019

vsk added reviewers for D57722: [Clang][NCF] Sanitizer options: helpers to check if {Kernel,Hardware}ASan is enabled: eugenis, kcc.
Feb 4 2019, 4:32 PM · Restricted Project
vsk accepted D57711: [Sanitizers] UBSan unreachable incompatible with Kernel ASan.

LGTM, thanks. It might make sense to add a predicate to SanitizerSet to make it easier to check when ASan is enabled, either pre-commit or as a follow-up.

Feb 4 2019, 2:09 PM · Restricted Project, Restricted Project

Feb 1 2019

vsk accepted D57489: [ASan] Do not instrument other runtime functions with `__asan_handle_no_return`.

Thanks, lgtm!

Feb 1 2019, 12:38 PM · Restricted Project, Restricted Project, Restricted Project
vsk added a comment to D57265: [PM/CC1] Add -f[no-]split-cold-code CC1 options to toggle splitting.

Ping.

Feb 1 2019, 10:30 AM · Restricted Project

Jan 31 2019

vsk added a comment to D57489: [ASan] Do not instrument other runtime functions with `__asan_handle_no_return`.

Looks reasonable to me.

Jan 31 2019, 11:04 AM · Restricted Project, Restricted Project, Restricted Project

Jan 29 2019

vsk accepted D57278: [Sanitizers] UBSan unreachable incompatible with ASan in the presence of `noreturn` calls.

LGTM, thanks!

Jan 29 2019, 2:03 PM · Restricted Project

Jan 28 2019

vsk added a comment to D57278: [Sanitizers] UBSan unreachable incompatible with ASan in the presence of `noreturn` calls.

Is it necessary to remove visitation of 'noreturn' call sites from ASan? I'd expect that to break non-C frontends which emit noreturn calls (rust/swift?).

Jan 28 2019, 5:41 PM · Restricted Project
vsk added inline comments to D57190: [MC] Teach the MachO object writer about N_FUNC_COLD.
Jan 28 2019, 9:14 AM

Jan 25 2019

vsk closed D57190: [MC] Teach the MachO object writer about N_FUNC_COLD.
Jan 25 2019, 4:57 PM
vsk updated the diff for D57265: [PM/CC1] Add -f[no-]split-cold-code CC1 options to toggle splitting.
  • Fix a think-o in a comment.
Jan 25 2019, 4:41 PM · Restricted Project
vsk added inline comments to D57190: [MC] Teach the MachO object writer about N_FUNC_COLD.
Jan 25 2019, 4:33 PM
vsk created D57265: [PM/CC1] Add -f[no-]split-cold-code CC1 options to toggle splitting.
Jan 25 2019, 4:30 PM · Restricted Project
vsk added a comment to D57050: [CodeGenPrepare] Handle all debug calls in dupRetToEnableTailCallOpts().

I see a minor issue in the test, but the patch looks great to me otherwise. Thanks!

Jan 25 2019, 9:56 AM

Jan 24 2019

vsk added a comment to D56624: [Sanitizers] UBSan unreachable incompatible with ASan in the presence of `noreturn` calls.
In D56624#1370607, @yln wrote:

Maybe the frontend should insert __asan_handle_noreturn whenever ASan is enabled, and then ASan would not care about the attribute? I'd like to avoid having this logic in two places.

+1 for this. @vsk Can you sign off on this design?

Jan 24 2019, 7:09 PM · Restricted Project
vsk added a comment to D57190: [MC] Teach the MachO object writer about N_FUNC_COLD.
In D57190#1370535, @pcc wrote:

Interesting, what's the advantage of this over doing something like creating a __cold section in the __TEXT segment?

Jan 24 2019, 6:49 PM
vsk updated the diff for D57190: [MC] Teach the MachO object writer about N_FUNC_COLD.

Per @pcc's suggestion, add basic AsmParser support for the .cold directive.

Jan 24 2019, 6:49 PM
vsk added a reviewer for D57190: [MC] Teach the MachO object writer about N_FUNC_COLD: mtrent.

+ Mike, who's touched nm recently.

Jan 24 2019, 4:23 PM
vsk added a comment to D57082: [HotColdSplit] Move splitting earlier in the pipeline.

I relaxed the test in r352138, and think that should address the issue.

Jan 24 2019, 4:21 PM
vsk added a comment to D56624: [Sanitizers] UBSan unreachable incompatible with ASan in the presence of `noreturn` calls.

Wouldn’t it be preferable to unpoison the stack inside of maybe_longjmp, once the opaque condition can be checked?

Sure, but that's not always possible. That's why we have interceptors.

Jan 24 2019, 4:19 PM · Restricted Project
vsk added a comment to D57082: [HotColdSplit] Move splitting earlier in the pipeline.

Sorry about that, taking a look now

Jan 24 2019, 4:08 PM
vsk added a comment to D56624: [Sanitizers] UBSan unreachable incompatible with ASan in the presence of `noreturn` calls.

Because "expect_noreturn" calls are allowed to return, the compiler must behave as they could. In particular, this means that unpoisoning the stack before expect_noreturn calls (given the current semantics) is premature.

I don't think that's true. A hypothetical function

maybe_longjmp(jmp_buf env)

that checks an opaque condition needs stack unpoisoning before the call, in the absense of a better solution.

Jan 24 2019, 2:52 PM · Restricted Project
vsk created D57190: [MC] Teach the MachO object writer about N_FUNC_COLD.
Jan 24 2019, 1:54 PM
vsk added a comment to D56624: [Sanitizers] UBSan unreachable incompatible with ASan in the presence of `noreturn` calls.
In D56624#1369940, @yln wrote:

Note that all of this currently only matters when compiling with -fsanitize=unreachable. The following discussion is within the context of the current implementation: UBSan removes the noreturn so it can instrument unreachable without the added instrumentation being optimized away. Maybe we should take a step back and ask if that is the right approach at all?

In D56624#1369795, @vsk wrote:

Because "expect_noreturn" calls are allowed to return, the compiler must behave as they could. In particular, this means that unpoisoning the stack before expect_noreturn calls (given the current semantics) is premature.

Put another way, a frontend author may (understandably, but mistakenly!) attach expect_noreturn to calls which they expect to be cold.

I think about this differently. Yes, most noreturn functions are also cold, e.g., abort, but not necessarily, e.g., calls to longjmp do not necessarily have to be. Why would it be okay to attach expect_noreturn instead of cold?

Jan 24 2019, 1:03 PM · Restricted Project
vsk added a comment to D56624: [Sanitizers] UBSan unreachable incompatible with ASan in the presence of `noreturn` calls.
In D56624#1369767, @yln wrote:
In D56624#1369635, @vsk wrote:

What are the advantages of a generalized expect_noreturn attribute, vs. a narrower attribute or intrinsic? The expect_noreturn semantics do not provide strong guarantees, and are not really orthogonal from the pre-existing cold attribute.

@eugenis Do you want to chime in here?
I think they convey different meanings even if their treatment by the optimizer is similar. The cold attribute says nothing about whether or not a function is expected to return.

Jan 24 2019, 11:21 AM · Restricted Project
vsk added a comment to D56624: [Sanitizers] UBSan unreachable incompatible with ASan in the presence of `noreturn` calls.

What are the advantages of a generalized expect_noreturn attribute, vs. a narrower attribute or intrinsic? The expect_noreturn semantics do not provide strong guarantees, and are not really orthogonal from the pre-existing cold attribute. In particular, expect_noreturn doesn't even seem strong enough to allow ASan to unpoison its stack.

Jan 24 2019, 10:29 AM · Restricted Project

Jan 23 2019

vsk created D57125: [HotColdSplit] Introduce a cost model to control splitting behavior.
Jan 23 2019, 3:48 PM
vsk updated the diff for D57082: [HotColdSplit] Move splitting earlier in the pipeline.
Jan 23 2019, 12:49 PM
vsk added inline comments to D57082: [HotColdSplit] Move splitting earlier in the pipeline.
Jan 23 2019, 12:49 PM
vsk added inline comments to D57082: [HotColdSplit] Move splitting earlier in the pipeline.
Jan 23 2019, 11:46 AM
vsk updated the diff for D57082: [HotColdSplit] Move splitting earlier in the pipeline.
  • Fix the pipeline issue in the old PM pointed out by Teresa. Add a test for it.
Jan 23 2019, 11:46 AM
vsk accepted D57092: [HotColdSplitting] Get DT and PDT from the pass manager..

Thanks! CTMark results look great, LGTM.

Jan 23 2019, 8:25 AM

Jan 22 2019

vsk created D57082: [HotColdSplit] Move splitting earlier in the pipeline.
Jan 22 2019, 8:12 PM
vsk added a comment to D57050: [CodeGenPrepare] Handle all debug calls in dupRetToEnableTailCallOpts().

Thanks for the patch. Could you please reduce the test case a bit further? There are kilobytes of debug info metadata here which don't appear necessary for reproducing the problem.

Jan 22 2019, 11:15 AM
Herald updated subscribers of D50593: ConstantMerge: merge common initial sequences.
Jan 22 2019, 11:14 AM

Jan 17 2019

vsk added a comment to D56045: [CodeExtractor] Emit lifetime markers around reloads of outputs.

Gentle ping (this isn't urgent, but it seems nice to have).

Jan 17 2019, 12:32 PM
vsk added a comment to D56865: [MergeFunc] Allow merging identical vararg functions using aliases.
In D56865#1362011, @rnk wrote:

Crazy idea: use musttail (only some targets support it) to make this work. Of course, first, make it correct.

Jan 17 2019, 11:53 AM
vsk created D56865: [MergeFunc] Allow merging identical vararg functions using aliases.
Jan 17 2019, 10:13 AM

Jan 16 2019

vsk created D56815: [FunctionComparator] Consider tail call kinds.
Jan 16 2019, 3:14 PM
vsk added a comment to D56764: handle invokes like calls for sample profile data.

(Looks reasonable to me. I haven't really touched this code, so it'd help if another review could +1 the change.)

Jan 16 2019, 2:50 PM
vsk added inline comments to D56764: handle invokes like calls for sample profile data.
Jan 16 2019, 12:17 PM

Jan 11 2019

vsk added a comment to D56587: Introduce DW_OP_LLVM_convert.

Thanks for the patch.

Jan 11 2019, 9:16 AM · Restricted Project, debug-info

Jan 10 2019

vsk created D56574: [MergeFunc] Erase unused duplicate functions if they are discardable.
Jan 10 2019, 7:01 PM