Displaying 7 results from an estimated 7 matches for "functiondifferenceengin".
Did you mean:
functiondifferenceengine
2011 Oct 29
0
[LLVMdev] [LLVM, llvm-diff] Question about FunctionDifferenceEngine and DiffConsumer::printValue
On Oct 28, 2011, at 2:00 AM, Stepan Dyatkovskiy wrote:
> I found next code when switch instruction differs:
>
> Engine.logf("right switch has extra case %r") << CaseValue;
>
> Where CaseValue is a ConstantInt object. Looking how logf works I found
> that it invokes DiffConsumer::printValue method for CaseValue. And here
> I found that CaseValue itself will
2011 Nov 03
0
[LLVMdev] [LLVM, llvm-diff] Question about FunctionDifferenceEngine and DiffConsumer::printValue
ping.
-Stepan.
Stepan Dyatkovskiy wrote:
> Hi,
>
> Please find the attached patch for review.
>
> -Stepan.
>
> John McCall wrote:
>> On Oct 28, 2011, at 2:00 AM, Stepan Dyatkovskiy wrote:
>>> I found next code when switch instruction differs:
>>>
>>> Engine.logf("right switch has extra case %r")<< CaseValue;
>>>
2011 Oct 28
2
[LLVMdev] [LLVM, llvm-diff] Question about FunctionDifferenceEngine and DiffConsumer::printValue
Hi all.
I found next code when switch instruction differs:
Engine.logf("right switch has extra case %r") << CaseValue;
Where CaseValue is a ConstantInt object. Looking how logf works I found
that it invokes DiffConsumer::printValue method for CaseValue. And here
I found that CaseValue itself will never printed. On first look how
DiffConsumer::printValue works it seems that for
2011 Oct 31
3
[LLVMdev] [LLVM, llvm-diff] Question about FunctionDifferenceEngine and DiffConsumer::printValue
Hi,
Please find the attached patch for review.
-Stepan.
John McCall wrote:
> On Oct 28, 2011, at 2:00 AM, Stepan Dyatkovskiy wrote:
>> I found next code when switch instruction differs:
>>
>> Engine.logf("right switch has extra case %r")<< CaseValue;
>>
>> Where CaseValue is a ConstantInt object. Looking how logf works I found
>> that it
2015 Jun 25
2
[LLVMdev] Any known-reliable numbering scheme for basic blocks?
...that equivalence class.
This seems related to a debate / bug-report
<https://llvm.org/bugs/show_bug.cgi?id=16043> regarding the arbitrary
nature of (pseudo?) labels in LLVM assembly. E.g.,*"; label:3"*.
It also looks like *llvm-diff* does something similar to what I want in its
*FunctionDifferenceEngine* class. But I think *llvm-diff* allows for the
two IR's to differ, and uses approximate matching. I don't need any
graceful degradation when the IR has changed, but I need exact matching
when the IR hasn't changed.
In the worst-case scenario, I could make a sweep through all of the...
2011 Feb 28
3
[LLVMdev] llvm-diff
...logic to llvm-diff, but it looks
like some heavy refactoring will be needed to do so. Who's the owner
of it?
There is too much logic in DifferenceEngine, classes being declared in
the cpp file, sub-classes of DifferenceEngine that could be used by
the metadata diff, but with the current style
(FunctionDifferenceEngine(*this)) will be hard to share.
I propose creating more files to split up the logic and use the
appropriate h/cpp split, even if that takes more space. I'm willing to
do some of this as part of my refactoring to get metadata diff, but I
need to know from the owner if that's ok or if he/she...
2011 Feb 28
0
[LLVMdev] llvm-diff
...t; like some heavy refactoring will be needed to do so. Who's the owner
> of it?
Me.
> There is too much logic in DifferenceEngine, classes being declared in
> the cpp file, sub-classes of DifferenceEngine that could be used by
> the metadata diff, but with the current style
> (FunctionDifferenceEngine(*this)) will be hard to share.
>
> I propose creating more files to split up the logic and use the
> appropriate h/cpp split, even if that takes more space. I'm willing to
> do some of this as part of my refactoring to get metadata diff, but I
> need to know from the owner if t...