Hi Sebastian! On 2026-03-26T20:45:46-0400, Sebastian Galindo <[email protected]> wrote: > In the following link I'm sharing the first draft for GSoC 2026 proposal. > > https://drive.google.com/file/d/1Mui6Lej8y6o8J4Vaua94s5x3bSSl9mRD/view?usp=sharing
Thanks! > Let me know your comments or which parts should I change. 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. I acknowledge that the OpenACC 'cache' directive, and OpenACC 'device_type' clause are more challenging than the other ones in your list. The good thing is that improvements/implementation can be done incrementally; 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. You've explicitly chosen the OpenACC features listed on our GSoC project ideas page -- which is fine, of course, but in case there are any other OpenACC features (from later OpenACC standard versions, for example) that you'd like to look into, that's also possible. It'll be good to add some more detail, be a bit more specific, regarding the individual implementation tasks. What you currently have is mostly relevant for your Task 1 -- and, I suppose, mostly sourced from my text on the GSoC project ideas page. 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? Once you've got the remaining hurdle sorted out, please add a little bit of text to demonstrate that you're able to build GCC with GPU code offloading, and use that to compile and run a simple program with GPU code offloading execution. Run the program with 'GOMP_DEBUG=1', 'GCN_DEBUG=1' set in the environment, to produce debugging output, showing GPU kernel launches. I appreciate your desire to do some bug fixing etc. during the Community Bonding period. Please add some text about other time commitments that you may have during project execution. 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? > Or if I should switch the writing style or something like that. That's fine. Grüße Thomas
