Hi Thomas, First of all, thanks for the review!
Just for completeness, might note that OpenACC middle end handling is not
only lowering/'gcc/omp-low.cc', but also other middle end code, and down
to the GPU back ends. Some "C++" things are missing next to "C" ones
that you mention. Also, 'libgomp/testsuite/' for runtime/execution test
cases, including all code offloading testing.
Ok, got it, thanks for the specification.
I'm fine to have those as "stretch goals" in the proposal,
and I agree to start with your Task 1, and then Task 3.
Great, maybe I'll include explicitly that I want these tasks to be
stretch goals.
Which parts of GCC do we need to touch
for Tasks 2, 3, 4: abstractly, and then in terms of GCC implementation
(to the extent that you're already able to understand)? For Task 2, is
there any existing non-OpenACC/OpenMP infrastructure in GCC that we may
be able to build upon?
Got it, I'll definitely include that, thanks!
Have you intentionally chosen to make this a 175 h (medium) project
instead of a 350 h (large) one? Is the end date of 2026-08-16 fixed, or
do we have some flexibility there, if needed?
I was looking at the official GSoC timeline to have a reference, but I
understand that the project could extend till November or something like
that. I have a lot of flexibility in that sense, and I would be happy to
work on it for a longer period.
According to that, do you think it would make more sense to define it as
a large project? I would be open to that. In that case, I would keep the
current tasks as the core goals, and extend the work to additional
OpenACC features depending on progress.
One concern I have is that, given the proposal deadline is close, I may
not be able to like fully specify the newer OpenACC features
implementation (Or yes?), maybe in a very abstract way.
Thanks for the input!
Best,
Sebastian
