Re: Memory access in GIMPLE

On Thu, Apr 3, 2025 at 2:23 AM Krister Walfridsson via Gcc wrote: > > I have more questions about GIMPLE memory semantics for smtgcc. > > As before, each section starts with a description of the semantics I've > implemented (or plan to implement), followed by concrete questions if > relevant. Let

Re: GSoC: Application Proposal for Simple File System for Nvidia and AMD GPU Code Testing

> > This expands on implementation details, compares different approaches > (in-memory vs. RPC-based solutions), and identifies relevant GCC components > to modify. > > 1. Overview of Implementation Approaches > > Currently, GCC’s GPU offloading test framework lacks support for file I/O, > causing

Memory access in GIMPLE

I have more questions about GIMPLE memory semantics for smtgcc. As before, each section starts with a description of the semantics I've implemented (or plan to implement), followed by concrete questions if relevant. Let me know if the described semantics are incorrect or incomplete. Accessi

GSoC

Dear Sir/Madam, I would like to work on the rust frontend for this summer. I am trying to break down all the steps for the first project in the rust frontend. So far I plan on creating the visitor class as stated and then using it to deal with all the different types of errors such as dead code, a

Re: GSoC 2025 – Excited About GCC Go Escape Analysis & Seeking Guidance

On Wed, Apr 2, 2025 at 6:35 AM Thomas Schwinge wrote: > > On 2025-03-31T19:48:16+0530, Astha Pipania via Gcc wrote: > > I hope you're doing well! > > Astha, welcome to GCC! > > > I'm incredibly excited about the "GCC Go Escape > > Analysis" project for GSoC 2025. > > ... which is listed on >

Re: GSoC OpenACC

Hi Carter! On 2025-03-30T22:00:41+, Carter Weidman via Gcc wrote: > My name is Carter. I’m looking to become active in the GCC community. Welcome to GCC! > I would of course love to be funded through GSoC (and will most definitely be > submitting a formal proposal) but will contribute reg

Re: GSoC: Application Proposal for Simple File System for Nvidia and AMD GPU Code Testing

Hi Ambika! Welcome to GCC! On 2025-03-29T15:26:18-0500, Ambika Sharan via Gcc wrote: > Simple File System for Nvidia and AMD GPU Code Generation Testing Thanks for your interest, and initial work on this project idea. Please add more detail: ideas how you think you'd implement the respective

Re: [GSoC][Enhance OpenACC support] Uncertain about Cache directive functionality and device_type clause goal

Hi Chenlu! On 2025-03-27T22:05:02+1100, Zhang lv via Gcc wrote: > Hi here, Welcome to GCC! > I found digging into OpenACC meaningful. It's a late start for a GSoC > proposal ..., but not yet too late! :-) > and any suggestions from the community are appreciated! Feel free > to comment on an

Re: GSOC interest in Extend the static analysis pass, [OpenACC]

Hi Kaaden! On 2025-03-10T22:20:21+, Kaaden Ruman via Gcc wrote: > Hello, my name is Kaaden and I am a student at the University of Alberta in > Canada. Welcome to GCC! > I am interested in pursuing the "Extend the static analysis pass" idea as a > medium size project. I'm sorry that I d

Re: GSoC mandatory step error

On Tue, Apr 01, 2025 at 10:09:56AM +0200, Martin Jambor wrote: > The simple fix is to initialize the variable to nullptr in the source, > of course. :-) It is a false positive. gimple *stmt; ... for (gsi = gsi_last_bb (bb); !gsi_end_p (gsi); gsi_prev (&gsi)) { stmt = gsi_stmt (gsi);

Re: GSoC mandatory step error

Hi Leul! On 2025-03-31T18:33:51-0400, Leul Abiy via Gcc wrote: > I just wanted to ask about the build of gcc. I know it is a required step > before applying to GCC for the GSoC 2025. However, I get an error. Welcome to GCC, and good luck for GSoC 2025! In addition to what Martin already wrote:

Re: GSoC 2025 – Excited About GCC Go Escape Analysis & Seeking Guidance

Hi Astha, Ian! On 2025-03-31T19:48:16+0530, Astha Pipania via Gcc wrote: > I hope you're doing well! Astha, welcome to GCC! > I'm incredibly excited about the "GCC Go Escape > Analysis" project for GSoC 2025. ... which is listed on