Displaying 5 results from an estimated 5 matches for "indutni".
Did you mean:
indutny
2018 Feb 24
2
CallSiteSplitting and musttail calls
Hello!
I've discovered that `CallSiteSplitting` optimization doesn't support
musttail calls. The easiest fix as it stands is disabling it for such call
sites: https://reviews.llvm.org/D43729 . However, I'm not happy with such
contribution.
My more sophisticated attempt has failed due to my poor understanding of
llvm internals. Here is the attempted patch:
2018 Feb 24
0
CallSiteSplitting and musttail calls
Update:
I was able to make progress on it today ( See
https://reviews.llvm.org/D43729 ). Apparently my problems were:
* Iterating through the instruction/block list after erasing
block/instruction
* Trying to split block after removing one predecessor
Regarding the latter, it appears that semantics of
`DuplicateInstructionsInSplitBetween` change significantly in such case,
and it starts to loop
2018 Feb 27
2
CallSiteSplitting and musttail calls
I think you realized this now, but to be clear:
More likely, you've found some bugs.
Unfortunately, not all of these utilities have good unit tests (though they
should!).
This would not be the first set of bugs people have found wrt to very
start/end of blocks, or bb == predbb issues.
On Sat, Feb 24, 2018 at 12:58 PM, Fedor Indutny via llvm-dev <
llvm-dev at lists.llvm.org> wrote:
2018 Feb 28
0
CallSiteSplitting and musttail calls
Hi,
On 27/02/2018 16:32, Daniel Berlin via llvm-dev wrote:
> I think you realized this now, but to be clear:
> More likely, you've found some bugs.
> Unfortunately, not all of these utilities have good unit tests (though
> they should!).
>
> This would not be the first set of bugs people have found wrt to very
> start/end of blocks, or bb == predbb issues.
>
2015 Aug 10
5
RFC: Add "operand bundles" to calls and invokes
We'd like to propose a scheme to attach "operand bundles" to call and
invoke instructions. This is based on the offline discussion
mentioned in
http://lists.cs.uiuc.edu/pipermail/llvmdev/2015-July/088748.html.
# Motivation & Definition
Our motivation behind this is to track the state required for
deoptimization (described briefly later) through the LLVM pipeline as
a