Displaying 4 results from an estimated 4 matches for "f90_array_type".
2013 Jan 18
2
[LLVMdev] Loads not hoisted out of the loop
...I'd rather we come up with something else.
How about having Fortran-specific metadata, and a Fortran-specific alias
analysis? The metadata could indicate how the properties of the
Fortran-frontend-generated types relate to the types that the IR code
uses to load/store data. For example:
f90_array_type = type { i32 size, double* data };
metadata = "attributes of f90_array_type, like restrict, should be
applied to the member pointer 'data'"
Is this something you've considered?
-Krzysztof
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
hosted by The...
2013 Jan 18
0
[LLVMdev] Loads not hoisted out of the loop
On Fri, Jan 18, 2013 at 10:00 AM, Krzysztof Parzyszek <
kparzysz at codeaurora.org> wrote:
> f90_array_type = type { i32 size, double* data };
I am not certain how fortran implements multi-dimensional arrays, but in my
case I'm doing something like
type { i32 nd, i32* dims, double* data };
Perhaps we could add !tbaa.pointer?
!1 = metadata !{ metadata !"int", metadata !0 }
!2 =...
2013 Jan 18
0
[LLVMdev] Loads not hoisted out of the loop
----- Original Message -----
> From: "Krzysztof Parzyszek" <kparzysz at codeaurora.org>
> To: "Dimitri Tcaciuc" <dtcaciuc at gmail.com>
> Cc: llvmdev at cs.uiuc.edu
> Sent: Friday, January 18, 2013 11:22:26 AM
> Subject: Re: [LLVMdev] Loads not hoisted out of the loop
>
> On 1/18/2013 11:11 AM, Dimitri Tcaciuc wrote:
> >
> > Right,
2013 Jan 18
2
[LLVMdev] Loads not hoisted out of the loop
On 1/18/2013 11:11 AM, Dimitri Tcaciuc wrote:
>
> Right, I see. Is there any other way to solve this? As the last resort,
> I was considering silently transforming each Array argument into
> separate data and metadata arguments, but that would certainly add other
> complications I'd rather avoid.
Depends on what information you have available. If all you have is the
LLVM IR,