Displaying 3 results from an estimated 3 matches for "funtimes".
Did you mean:
runtimes
2020 Jan 22
2
Inlining + CSE + restrict pointers == funtimes
...nkel, Hal J. <hfinkel at anl.gov>
> *Sent:* Wednesday, January 22, 2020 17:33
> *To:* Jeroen Dobbelaere <dobbel at synopsys.com>; Neil Henning <
> neil.henning at unity3d.com>; llvm-dev at lists.llvm.org
> *Subject:* Re: [llvm-dev] Inlining + CSE + restrict pointers == funtimes
>
>
>
> At a high level, EarlyCSE should be intersecting the metadata of
> instructions that it combines. If it doesn't, and also doesn't drop the
> metadata, that seems like a bug, regardless of anything else.
>
> On 1/22/20 9:30 AM, Jeroen Dobbelaere wrote:
>
&g...
2020 Jan 22
2
Inlining + CSE + restrict pointers == funtimes
...es at lists.llvm.org><mailto:llvm-dev-bounces at lists.llvm.org> On Behalf Of Neil Henning via llvm-dev
Sent: Wednesday, January 22, 2020 14:02
To: llvm-dev <llvm-dev at lists.llvm.org><mailto:llvm-dev at lists.llvm.org>
Subject: [llvm-dev] Inlining + CSE + restrict pointers == funtimes
So I've been narrowing down a very fun issue in our Burst compiler stack with respect to noalias support, and I've managed to basically boil this down to the following failure (see https://godbolt.org/z/-mdjPV<https://urldefense.proofpoint.com/v2/url?u=https-3A__godbolt.org_z_-2DmdjPV&a...
2020 Jan 22
4
Inlining + CSE + restrict pointers == funtimes
So I've been narrowing down a very fun issue in our Burst compiler stack
with respect to noalias support, and I've managed to basically boil this
down to the following failure (see https://godbolt.org/z/-mdjPV):
int called(int* __restrict__ a, int* b, int* c) {
return *a + *b + *c;
}
int foo(int * x, int * y) {
return *x + *y + called(x, x, y);
}
int bar(int * x, int * y) {
return