This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [RFC] Offloading Support in libgomp


> What I meant was just that if you call GOMP_target with
> num_descs N, then the structure will look like:
> struct .omp_target_data
> {
>   sometype0 *var0;
>   sometype1 *var1;
>   ...
>   sometypeNminus1 *varNminus1;
> };
> so pretty much the runtime will call the target routine with address of
> an array of N pointers, and the compiler generated target routine will
> just use a struct to access it to make it more debuggable.  As there won't
> be any paddings in the structure, I'd hope the structure layout will be
> exactly the same as the array.
Ok, such assumption about struct layout seems to be enough for runtime
to figure out what to translate.
I'll try to put to rights everything we've discussed and prepare some
description of the overall scheme.  After that, if you are ok with that,
we could start implementing it - that's the time we'll face the most
interesting stuff I guess:)

Thanks, Michael


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]