Displaying 15 results from an estimated 15 matches for "bsteinbr".
2015 Mar 01
2
[LLVMdev] RFC: PerfGuide for frontend authors
> On Mar 1, 2015, at 7:53 AM, Björn Steinbrink <bsteinbr at gmail.com> wrote:
>
> On 2015.02.28 18:17:27 -0800, Philip Reames wrote:
>>> On Feb 28, 2015, at 3:01 PM, Björn Steinbrink <bsteinbr at gmail.com> wrote:
>>> 2015-02-28 23:50 GMT+01:00 Philip Reames <listmail at philipreames.com>:
>>>>>>...
2015 Mar 01
2
[LLVMdev] RFC: PerfGuide for frontend authors
> On Feb 28, 2015, at 3:01 PM, Björn Steinbrink <bsteinbr at gmail.com> wrote:
>
> [This time without dropping the list, sorry]
>
> 2015-02-28 23:50 GMT+01:00 Philip Reames <listmail at philipreames.com>:
>
>>>> On Feb 28, 2015, at 2:30 PM, Björn Steinbrink <bsteinbr at gmail.com> wrote:
>>>>
>&...
2015 Feb 28
0
[LLVMdev] RFC: PerfGuide for frontend authors
[This time without dropping the list, sorry]
2015-02-28 23:50 GMT+01:00 Philip Reames <listmail at philipreames.com>:
>> On Feb 28, 2015, at 2:30 PM, Björn Steinbrink <bsteinbr at gmail.com> wrote:
>>
>>> On 2015.02.28 14:23:02 -0800, Philip Reames wrote:
>>>> On 02/28/2015 10:04 AM, Björn Steinbrink wrote:
>>>> Hi,
>>>>
>>>>> On 2015.02.28 10:53:35 -0600, Hal Finkel wrote:
>>>>> ----- Ori...
2017 Jan 31
1
Folding zext from i1 into PHI nodes with only zwo incoming values.
2017-01-31 16:59 GMT+01:00 Sanjay Patel <spatel at rotateright.com>:
>
>
> On Tue, Jan 31, 2017 at 3:09 AM, Björn Steinbrink <bsteinbr at gmail.com>
> wrote:
>
>> Hi Sanjay,
>>
>> 2017-01-30 22:22 GMT+01:00 Sanjay Patel <spatel at rotateright.com>:
>>
>>> My minimal patch idea is to ease the restriction in ShouldChangeType
>>> because i1 is special. I tried the patch below,...
2015 Feb 28
2
[LLVMdev] RFC: PerfGuide for frontend authors
> On Feb 28, 2015, at 2:30 PM, Björn Steinbrink <bsteinbr at gmail.com> wrote:
>
>> On 2015.02.28 14:23:02 -0800, Philip Reames wrote:
>>> On 02/28/2015 10:04 AM, Björn Steinbrink wrote:
>>> Hi,
>>>
>>>> On 2015.02.28 10:53:35 -0600, Hal Finkel wrote:
>>>> ----- Original Message -----
>&g...
2017 Jan 31
0
Folding zext from i1 into PHI nodes with only zwo incoming values.
On Tue, Jan 31, 2017 at 3:09 AM, Björn Steinbrink <bsteinbr at gmail.com>
wrote:
> Hi Sanjay,
>
> 2017-01-30 22:22 GMT+01:00 Sanjay Patel <spatel at rotateright.com>:
>
>> My minimal patch idea is to ease the restriction in ShouldChangeType
>> because i1 is special. I tried the patch below, and it works on the
>> exam...
2015 Jan 22
5
[LLVMdev] Why does "uwtable" prevent optimizing Invoke -> Call?
Hi,
in r176827 the optimization that turns invokes with empty landing pads
into plain calls was disabled for invocations of function with the
"uwtable" attribute.
But given this code:
struct S { ~S() {}; };
void blackbox();
__attribute__((__noinline__)) void inner() { blackbox(); }
int foo() {
S s;
inner();
return 0;
}
int bar() {
2017 Jan 31
2
Folding zext from i1 into PHI nodes with only zwo incoming values.
Hi Sanjay,
2017-01-30 22:22 GMT+01:00 Sanjay Patel <spatel at rotateright.com>:
> My minimal patch idea is to ease the restriction in ShouldChangeType
> because i1 is special. I tried the patch below, and it works on the
> example...and nothing in 'make check' failed. :)
>
Yeah, that would work for me as well, I just wasn't sure about the
implications that has.
2015 Aug 28
2
get llvm IR after a clang optimization pass.
Hi,
Id like to run clang with some optimization passes (-reassociate,
-simplifycfg, -dce
)
But in the end I need to dump the llvm IR (no link to assembly generation).
I didnt find any way to do that.
I found out that passes are run via opt, but opt generates bc code, and I
want IR.
Any help will be welcome
Thanks,
Régis
-------------- next part
2015 Oct 05
2
Swift to IR, generates wrong IR
Hi,
2015-10-05 11:49 GMT+02:00 Rinaldini Julien via llvm-dev
<llvm-dev at lists.llvm.org>:
> Sorry, the error is (the previous one was from Apple’s lli):
>
> Documents/strong.codes/code/build/obfuscator-llvm/bin/opt: test.ll:57:203: error: expected comma after getelementptr's type
> @_METACLASS_DATA__TtC4test13TipCalculator = private constant { i32, i32, i32, i32, i8*, i8*,
2015 Feb 28
0
[LLVMdev] RFC: PerfGuide for frontend authors
On 2015.02.28 14:23:02 -0800, Philip Reames wrote:
> On 02/28/2015 10:04 AM, Björn Steinbrink wrote:
> >Hi,
> >
> >On 2015.02.28 10:53:35 -0600, Hal Finkel wrote:
> >>----- Original Message -----
> >>>From: "Philip Reames" <listmail at philipreames.com>
> >>>>6. Use the lifetime.start/lifetime.end and
>
2017 Jan 30
0
Folding zext from i1 into PHI nodes with only zwo incoming values.
...ller to a larger illegal type.
+/// a smaller to a larger illegal type. i1 is always treated as a legal
type.
bool InstCombiner::ShouldChangeType(Type *From, Type *To) const {
assert(From->isIntegerTy() && To->isIntegerTy());
On Mon, Jan 30, 2017 at 1:22 PM, Björn Steinbrink <bsteinbr at gmail.com>
wrote:
> Hi Sanjay,
>
> unfortunately that patch does not help in my case. Here's the IR that
> fails to get fully optimized:
>
> target datalayout = "e-m:e-i64:64-f80:128-n8:16:32:64-S128"
> target triple = "x86_64-unknown-linux-gnu...
2015 Feb 28
2
[LLVMdev] RFC: PerfGuide for frontend authors
On 02/28/2015 10:04 AM, Björn Steinbrink wrote:
> Hi,
>
> On 2015.02.28 10:53:35 -0600, Hal Finkel wrote:
>> ----- Original Message -----
>>> From: "Philip Reames" <listmail at philipreames.com>
>>>> 6. Use the lifetime.start/lifetime.end and
>>>> invariant.start/invariant.end intrinsics where possible
>>> Do you find these
2017 Jan 30
3
Folding zext from i1 into PHI nodes with only zwo incoming values.
Hi Sanjay,
unfortunately that patch does not help in my case. Here's the IR that fails
to get fully optimized:
target datalayout = "e-m:e-i64:64-f80:128-n8:16:32:64-S128"
target triple = "x86_64-unknown-linux-gnu"
define fastcc zeroext i1 @testfunc(i8** noalias nocapture readonly
dereferenceable(8)) unnamed_addr {
entry-block:
%1 = load i8*, i8**
2015 Feb 28
0
[LLVMdev] RFC: PerfGuide for frontend authors
Hi,
On 2015.02.28 10:53:35 -0600, Hal Finkel wrote:
> ----- Original Message -----
> > From: "Philip Reames" <listmail at philipreames.com>
> > > 6. Use the lifetime.start/lifetime.end and
> > > invariant.start/invariant.end intrinsics where possible
> > Do you find these help in practice? The few experiments I ran were
> > neutral at best