Displaying 7 results from an estimated 7 matches for "allocmemori".
Did you mean:
allocmemory
2016 Jan 04
3
Can someone give me some pointer on alias analysis ?
2015-12-26 18:32 GMT+01:00 Philip Reames <listmail at philipreames.com>:
> On 12/26/2015 02:17 AM, Amaury SECHET via llvm-dev wrote:
>
> I'm trying to fix that bug: https://llvm.org/bugs/show_bug.cgi?id=20049
>
> It turns out this is the kind of optimization that I really need, as when
> it isn't done, all kind of other optimizations opportunities down the road
2015 Dec 26
2
Can someone give me some pointer on alias analysis ?
I'm trying to fix that bug: https://llvm.org/bugs/show_bug.cgi?id=20049
It turns out this is the kind of optimization that I really need, as when
it isn't done, all kind of other optimizations opportunities down the road
are not realized as they are not exposed.
I have no idea where to start digging for this. I assume there is some kind
of interaction between memory dependency and alias
2015 Aug 20
3
[RFC] Aggreate load/store, proposed plan
----- Original Message -----
> From: "Mehdi Amini via llvm-dev" <llvm-dev at lists.llvm.org>
> To: "deadal nix" <deadalnix at gmail.com>
> Cc: "llvm-dev" <llvm-dev at lists.llvm.org>
> Sent: Wednesday, August 19, 2015 7:24:28 PM
> Subject: Re: [llvm-dev] [RFC] Aggreate load/store, proposed plan
>
> Hi,
>
> To be sure,
2016 Jan 04
3
Can someone give me some pointer on alias analysis ?
On 01/04/2016 07:32 AM, Amaury SECHET wrote:
> After a bit more investigation, it turns out that because %0 is stored
> into %1 (after bitcast) and so %3 may have access to it and clobber it.
Can you give a bit more context? I'm not sure which of the examples
you're talking about.
>
> After a bit of thought, it is correct in the general case, but
> definitively something
2015 Aug 20
2
[RFC] Aggreate load/store, proposed plan
----- Original Message -----
> From: "deadal nix" <deadalnix at gmail.com>
> To: "Hal Finkel" <hfinkel at anl.gov>
> Cc: "Mehdi Amini" <mehdi.amini at apple.com>, "llvm-dev" <llvm-dev at lists.llvm.org>
> Sent: Thursday, August 20, 2015 4:09:17 PM
> Subject: Re: [llvm-dev] [RFC] Aggreate load/store, proposed plan
>
2015 Aug 21
3
[RFC] Aggreate load/store, proposed plan
----- Original Message -----
> From: "deadal nix" <deadalnix at gmail.com>
> To: "Hal Finkel" <hfinkel at anl.gov>
> Cc: "Mehdi Amini" <mehdi.amini at apple.com>, "llvm-dev" <llvm-dev at lists.llvm.org>
> Sent: Friday, August 21, 2015 1:24:04 AM
> Subject: Re: [llvm-dev] [RFC] Aggreate load/store, proposed plan
>
2015 Aug 20
2
[RFC] Aggreate load/store, proposed plan
It is pretty clear people need this. Let's get this moving.
I'll try to sum up the point that have been made and I'll try to address
them carefully.
1/ There is no good solution for large aggregates.
That is true. However, I don't think this is a reason to not address
smaller aggregates, as they appear to be needed. Realistically, the
proportion of aggregates that are very large