Re: Gsoc: Fortran-Do Concurrent

Hello, we are delighted you found contributing to GCC interesting. On Thu, Mar 13 2025, ahmad tariq via Gcc wrote: > Hi, > I'm Ahmad Abdul Rehman, a third year computer science undergraduate from > FAST(Pakistan). I am interested in the "Do-Concurrent" project, and I > noticed that some work has

Re: GSoC 2025 Rust Front-End: Name Resolution Pass Rewrite

Hello, we are delighted you found contributing to GCC interesting. On Sun, Mar 16 2025, Christina / via Gcc wrote: > Hello! I'm interested in the idea of "Name Resolution Pass Rewrite". > I took the compiler course and implemented a ALGOL-like language compiler. > I have huge passion about compil

Re: [GSOC 2025] Interests in extending the static analysis pass(es): support for C++ or CPython API

On Wed, Mar 19, 2025 at 10:46 PM zzmic wrote: > > Dear all, > > > I hope you’ve been doing well! > > I’m Zhiwen, an undergraduate who is working towards his degree jointly in > mathematics and computer science. > > > I’m writing to express my interest in working on a medium-sized (or > large-siz

Re: (GSoC) I am interested in contributing to GCC's Rust Front-End

Hello, On Wed, Mar 12 2025, Joey Pandina via Gcc wrote: > Dear GCC representative, > My name is Joey and I am a senior Computer Science student at Washington > State University. I am interested in contributing to GCC this summer. Last > semester, I took a class on compilers and thoroughly enjoyed

Re: [GSoC] Proposal Discussion:Fortran – run-time argument checking

Hello, we are delighted you found contributing to GCC interesting. On Mon, Mar 03 2025, Gwen Fu via Gcc wrote: > Dear GCC Community: > I hope this email finds you well. My name is Gwen Fu(or Pengrui Fu), and I > am interested in participating in Google Summer of Code 2025 with GCC. I am > writing

Re: [GSoC][Fortran – DO CONCURRENT] Interest in 2025 GSoC – Fortran DO CONCURRENT Auto-Parallelization

Hello, On Mon, Mar 10 2025, Zhang lv via Gcc wrote: > Hi here, > > I'm a Master of Computer Science student at the University of Melbourne. > Previously, I worked on implementing a GCC optimization prefetching pass > (which involved loop unrolling) for an Alpha-like computer architecture. > I'm s

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

Kaaden Ruman via Gcc writes: > Hello, my name is Kaaden and I am a student at the University of Alberta in > Canada. I am interested in pursuing the "Extend the static analysis pass" > idea as a medium size project. > > I have cloned and built gcc and ran the testsuite and would like a > nudge

Re: GSOC: Guidance on LTO, and Static Analysis Projects

Yatindra Indoria via Gcc writes: > Hello, > > I am an engineering student. I’ve worked on high frequency trading systems, > and (research) on the Linux kernel I/O and memory subsystems. I am looking > to start contributing to GCC, for quite some time now, as my work utilises > it extensively :) >

Re: GSOC interest in Extend the static analysis pass

Basile Starynkevitch writes: > hello > > You could take (and improve/refactor) some obsolete code from > https://github.com/bstarynk/bismon > and read the below draft report > http://www.starynkevitch.net/Basile/bismon-chariot-doc.pdf > > I am no more working on that code base. > Let's not sugge

Re: GSoC 2025: In-Memory Filesystem for GPU Offloading Tests

On 10/03/2025 15:37, Arijit Kumar Das via Gcc wrote: Hello GCC Community! I am Arijit Kumar Das, a second-year engineering undergraduate from NIAMT Ranchi, India. While my major isn’t Computer Science, my passion for system programming, embedded systems, and operating systems has driven me towar

Re: GSoC 2025: In-Memory Filesystem for GPU Offloading Tests

On 10/03/2025 22:56, Arijit Kumar Das wrote: Hello Andrew, Thank you for the detailed response! This gives me a much clearer picture of how things work. Regarding the two possible approaches: * I personally find *Option A (self-contained in-memory FS)* more interesting, and I'd like to

Re: GSoC 2025: In-Memory Filesystem for GPU Offloading Tests

Hello Andrew, Thank you for the detailed response! This gives me a much clearer picture of how things work. Regarding the two possible approaches: - I personally find *Option A (self-contained in-memory FS)* more interesting, and I'd like to work on it first. - However, if *Option B

Re: [GSoC][Rewrite Rust lints]: Suggestions to get started

Hi, On Sat, Mar 01 2025, 岡田隆太郎 via Gcc wrote: > Hello, > > My name is Ryutaro Okada. I am interested in participating in Google Summer > of Code 2024 with the GCC organization. Presumably 2025? ;-) > I am particularly fascinated by the > project "Rewrite Rust lints to operate on our frontend's H

Re: GSoC "Nothrow detection" proposal review

Hello, On Fri, Apr 05 2024, PRANIL DEY wrote: > Hello GCC Community, > I am Pranil Dey and I had submitted a proposal for the project "Improve > nothrow detection in GCC", but as the deadline period was a holiday time I > wanted to ask you to review my proposal now. > I am already getting familiar

Re: [GSoC] Application RFC + Question - GENERIC dump

> On Tue, Apr 2, 2024 at 11:14 AM Thor Preimesberger via Gcc > >> wrote: > >> > > >> > Forgot to CC the mailing list - mea culpa. > >> > > >> > -- Forwarded message - > >> > From: Thor Preimesberger > &g

Re: [GSoC] Application RFC + Question - GENERIC dump

pa. >> > >> > -- Forwarded message - >> > From: Thor Preimesberger >> > Date: Tue, Apr 2, 2024 at 5:57 PM >> > Subject: Re: [GSoC] Application RFC + Question - GENERIC dump >> > To: Richard Biener >> > >> > >> > Tha

Re: [GSoC] Application RFC + Question - GENERIC dump

> > Date: Tue, Apr 2, 2024 at 5:57 PM > > Subject: Re: [GSoC] Application RFC + Question - GENERIC dump > > To: Richard Biener > > > > > > Thanks for the quick feedback, especially on such short notice - I'll > > get the actual GSoC application in, within

Re: GSoC Timeline Review

Hi Nada, Apologies for not being able to reply earlier as well. I’m glad to hear you’re interested in continuing this project! There is still a lot of work to be done — my work from last summer is in a very prototype stage. As David mentioned, familiarizing myself with the analyzer took some time,

Re: [GSoC] Interest in applying

Hello, On Sun, Mar 31 2024, tmpod via Gcc wrote: > Hello, > > I am a Computer Science student, currently taking a Master's degree in > > > Portugal's top university. I have a

Re: GSoC Timeline Review

Hello, On Sat, Mar 30 2024, Nada Elsayed via Gcc wrote: > I think that I didn't fully understand the project, so I read more and > updated the Timeline Suggestion. Sorry that we were for not being able to respond sooner, Easter got into way in an unfortunate way. I do not know much about Cython

Re: GSoC Timeline Review

On Tue, 2024-04-02 at 10:06 -0400, David Malcolm wrote: > What timezone are you in?  (I'm in EDT, UTC+4) Sorry, that should be UTC-4 (on the east coast of the US) Dave

Re: GSoC Timeline Review

On Sat, 2024-03-30 at 13:54 +0200, Nada Elsayed wrote: > I think that I didn't fully understand the project, so I read more > and > updated the Timeline Suggestion. Hi Nada I'm very sorry for not responding sooner; I've been dealing with an difficult issue that's arisen outside of my computer wo

Re: [GSoC] Application RFC + Question - GENERIC dump

On Tue, Apr 2, 2024 at 11:14 AM Thor Preimesberger via Gcc wrote: > > Forgot to CC the mailing list - mea culpa. > > -- Forwarded message - > From: Thor Preimesberger > Date: Tue, Apr 2, 2024 at 5:57 PM > Subject: Re: [GSoC] Application RFC + Question - GENER

Re: [GSoC] Application RFC + Question - GENERIC dump

On Mon, Apr 1, 2024 at 6:23 PM Thor Preimesberger via Gcc wrote: > > Hey all, > > I'm joining the group of people submitting their GSoC applications > over the holiday. I'm interested in the "Implement structured dumping > of GENERIC" project idea, and the application I've written is below. T

Re: "GSoC"

Hello, I actually forgot to CC the mailing list as I promised to, so re-sending. Sorry, Martin On Sat, Mar 30 2024, Martin Jambor wrote: > Hello, > > and sorry for replying late, I have faced a few urgent interruptions > last week and unfortunately it is also a short week because of Easter - >

Re: GSoC

Hello Abhinav, sorry for a very brief answer, I'm not much online during Easter (the timing of the application deadline is a bit unfortunate in this regard). On Sat, Mar 30 2024, Abhinav Gupta wrote: > Hello GCC community, > Since resuming work for the GSoC proposal recently, I have made > s

Re: GSoC 2024 [Fortran - DO CONCURRENT] Seeking feedback/suggestions for project proposal

Hello Anuj, On Thu, Mar 28 2024, Anuj Mohite wrote: > Hi, > I'm Anuj M, an undergraduate student interested in participating in GSoC > 2024 with GCC. I would like to work on the project improving the DO > CONCURRENT construct in the GFortran compiler.The current implementation in > GFortran has li

Re: GSoC

Hello GCC community, Since resuming work for the GSoC proposal recently, I have made significant progress in understanding the code snippets provided by Mr. Jambor and delved into the libgomp folder, compiling random snippets in the examples folder and reading the IR. Building GCC from source

Re: GSoC Timeline Review

I think that I didn't fully understand the project, so I read more and updated the Timeline Suggestion. Suggested Timeline: - May 1-26: - Explore Cython modules and try more realistic codes to see how it translates Python to c/c++. - Know more about entry-point

Re: "GSoC"

Thanks, I'll check them out. On Mon, 25 Mar 2024, 9:50 pm Martin Jambor, wrote: > Hello, > > On Sun, Mar 24 2024, M Hamza Nadeem via Gcc wrote: > > Hi Sir / mam, > > > > > > I hope this email finds you well. As an enthusiastic contributor with a > > strong grasp of C/C++ and familiarity with Rus

Re: "GSoC"

Hello, On Sun, Mar 24 2024, M Hamza Nadeem via Gcc wrote: > Hi Sir / mam, > > > I hope this email finds you well. As an enthusiastic contributor with a > strong grasp of C/C++ and familiarity with Rust, I am eager to explore > potential projects for Google Summer of Code (GSoC) 2024 within the GNU

Re: GSoC

On Sat, Mar 23 2024, koushiki khobare via Gcc wrote: > Respected sir, > > I am Koushiki Khobare from India and currently a first year > student(Computer Science Student) studying in Pune Institute of > Computer Technology, Pune, Maharashtra. Recently I heard about GSoC > and got very excited to exp

Re: GSoC

Hi Abhinav! Thanks for your interest in contributing to GCC, and thanks to Martin for all the information you already provided. Just a bit more, to get you started on developing a proper project proposal: On 2024-03-13T14:54:52+0100, Martin Jambor wrote: > On Tue, Mar 12 2024, Abhinav Gupta wro

Re: GSoC

Hello, On Tue, Mar 12 2024, Abhinav Gupta wrote: > Hi! Thank you for replying to my request! > I looked at all the links you provided in the reply and read the > paper cited on the GCC page for GSoC. I also looked into the rust > frontend project during this time, and the Offloading project >

Re: GSoC

Hello, On Wed, Mar 06 2024, Abhinav Gupta via Gcc wrote: > Dear GCC Community, > I hope this email finds you well. My name is Abhinav Gupta. I am a > 3rd-year student at IIT Tirupati pursuing a bachelor's degree in > computer science and engineering. I am writing to express my interest > in co

Re: [GSoC][Improve nothrow detection]: Suggestions to get started

Ping for [GSoC][Improve nothrow detection]: Suggestions to get started. Could you please take a look when you get a chance? Sincerely, Ken Matsui On Wed, Feb 28, 2024 at 8:00 AM Ken Matsui wrote: > > Hi Jan, > > My name is Ken Matsui. I am highly interested in contributing to your > GSoC 2024

Re: GSoC 2024 Expression of interes

Hello, On Wed, Feb 28 2024, Aditya Ballaki via Gcc wrote: > Hi Team, > > I'm an incoming graduate student in Computer Engineering at Cornell > University, and I'm keen on participating in GSOC by contributing to > open-source projects before starting my graduate program. Wonderful, welcome! > Sp

Re: GSOC

Hello, On Tue, Feb 27 2024, Pratush Rai via Gcc wrote: > I want to work on the Rust Front End project as per the idea list. I am a > rust compiler contributor and want to start contributing to gcc. > I need some guidance on how to start. Please note that Rust-GCC projects are a bit special in the

Re: GSoC 2024 Application: Rupali Paliwal

Hello, We are delighted you found contributing to GCC interesting. GCC has applied to be part of GSoC 2024 but of course selected organizations have not been announced yet this year. More comments inline. On Mon, Jan 22 2024, Rupali P via Gcc wrote: > Respected GSoC Review Team, > > > I am writi

Re: GSoC: Application for Rust Front-End Project at GCC

Hello Arpit, We are very happy that you found contributing to GCC-rust interesting. GCC has applied to be part of GSoC 2024 but of course selected organizations have not been announced yet this year. On Sat, Dec 30 2023, CS21B062 ARPIT GUPTA wrote: > Dear GCC Community, > > I hope this email fin

Re: GSoc Topics

Thanks, I'll check them out. On Wed, 24 Jan, 2024, 03:52 Martin Jambor, wrote: > Hello, > > We are delighted you found contributing to GCC interesting. GCC has > applied to be part of GSoC 2024 but of course selected organizations > have not been announced yet. > > On Fri, Jan 12 2024, Gaurang

Re: GSoc Topics

Hello, We are delighted you found contributing to GCC interesting. GCC has applied to be part of GSoC 2024 but of course selected organizations have not been announced yet. On Fri, Jan 12 2024, Gaurang Aswal via Gcc wrote: > Hey I am Gaurang Aswal a 4th year B.E. Computer Science student from BI

Re: GSoC: Application for Rust Front-End Project at GCC

Hi Arpit! First, welcome to GCC, and I appreciate your enthousiasm! On 2023-12-30T22:30:37+0530, CS21B062 ARPIT GUPTA wrote: > Dear GCC Community, > > I hope this email finds you well. My name is Arpit and I am writing to > express my interest in participating in GSoC, specifically for the > Rus

Re: Re: GSoC: want to take part in `Extend the static analysis pass for CPython Extension`

Thanks Martin! Sounds good; I submitted my proposal unchanged for now (i.e assuming an independent project), but as Dave mentioned in another thread, it may be divided into several logical components, perhaps with certain features extended, to be suited for collaboration. Best, Eric On Mon, A

Re: [GSOC] few question about Bypass assembler when generating LTO object files

> Thanks to Martin, Honza, and Théo for your feedback. I have incorporated > almost all of it, updated my proposal accordingly, and submitted it. > Regarding grammar errors, I have fixed many, but there may still be some > left (I could be better at grammar, to be honest :( ). I could be better to

Re: [GSOC] few question about Bypass assembler when generating LTO object files

Thanks to Martin, Honza, and Théo for your feedback. I have incorporated almost all of it, updated my proposal accordingly, and submitted it. Regarding grammar errors, I have fixed many, but there may still be some left (I could be better at grammar, to be honest :( ). On Tue, 4 Apr 2023 at 15:55,

Re: [GSOC] few question about Bypass assembler when generating LTO object files

Hello, > Thanks, Jan for the Reply! I have completed a draft proposal for this > project. I will appreciate your's, Martin's, or anybody else feedback on > the same. > Here is the link to my proposal > https://docs.google.com/document/d/1r9kzsU96kOYfIhWZx62jx4ALG-J_aJs5U0sDpwFUtts/edit?usp=sharing

Re: [GSOC] few question about Bypass assembler when generating LTO object files

Hi, On Tue, Apr 04 2023, Rishi Raj wrote: > Thanks, Jan for the Reply! I have completed a draft proposal for this > project. I will appreciate your's, Martin's, or anybody else feedback on > the same. > Here is the link to my proposal > https://docs.google.com/document/d/1r9kzsU96kOYfIhWZx62jx4ALG

Re: [GSoC][analyzer-c++] Submission of a draft proposal

On Mon, 2023-04-03 at 18:46 +0200, Benjamin Priour wrote: > Following last mail, a classic I forgot to link my draft ! > https://docs.google.com/document/d/1MaLDo-Rt8yrJIvC1MO8SmFc6fp4eRQM_JeSdv-1kbsc/edit?usp=sharing Some notes: * The document still has some notes in italics marked "[RFC]" whic

Re: [GSOC] few question about Bypass assembler when generating LTO object files

Thanks, Jan for the Reply! I have completed a draft proposal for this project. I will appreciate your's, Martin's, or anybody else feedback on the same. Here is the link to my proposal https://docs.google.com/document/d/1r9kzsU96kOYfIhWZx62jx4ALG-J_aJs5U0sDpwFUtts/edit?usp=sharing On Tue, 4 Apr 20

Re: [GSOC] few question about Bypass assembler when generating LTO object files

Hello, > While going through the patch and simple-object.c I understood that the > file simple-object.c is used to handle the object file format. However, > this file does not contain all the architecture information required for > LTO object files, so the workaround used in the patch is to read th

RE: GSoC Separate Host Process Offloading

Hi Adi! I've not been able yet to review your items in detail, but it's very good that you're discussing your ideas! At least a few comments: On 2023-04-01T03:16:28+, "Prasad, Adi via Gcc" wrote: > Tobias wrote: >> [...] permit something like -foffload=host instead of having to >> specify -

Re: [GSOC] few question about Bypass assembler when generating LTO object files

While going through the patch and simple-object.c I understood that the file simple-object.c is used to handle the object file format. However, this file does not contain all the architecture information required for LTO object files, so the workaround used in the patch is to read the crtbegin.o fi

RE: GSoC Separate Host Process Offloading

m: Prasad, Adi >> Sent: Saturday, April 1, 2023 4:16 AM >> To: 'Tobias Burnus' ; Thomas Schwinge >> >> Cc: gcc@gcc.gnu.org >> Subject: RE: GSoC Separate Host Process Offloading >> >> Hi Tobias, >> Thanks for the reply! &

Re: [GSoC][analyzer-c++] Submission of a draft proposal

Following last mail, a classic I forgot to link my draft ! https://docs.google.com/document/d/1MaLDo-Rt8yrJIvC1MO8SmFc6fp4eRQM_JeSdv-1kbsc/edit?usp=sharing Best, Benjamin. On Mon, Apr 3, 2023 at 6:44 PM Benjamin Priour wrote: > Hi David, > > On Mon, Apr 3, 2023 at 12:38 AM David Malcolm wrote:

Re: [GSoC][analyzer-c++] Submission of a draft proposal

Hi David, On Mon, Apr 3, 2023 at 12:38 AM David Malcolm wrote: > > To be fair, C ones can be as well; the analyzer's exploded graphs tend > to get very big on anything but the most trivial examples. > > > [...snip...] > > Indeed - you'll have to do a lot of looking at gimple IR dumps, what > t

Re: GSoC Separate Host Process Offloading

Hi Tobias and Thomas - just wondering if you've had a chance to look at this? Thanks, Adi From: Prasad, Adi Sent: Saturday, April 1, 2023 5:16 am To: Tobias Burnus ; Thomas Schwinge Cc: gcc@gcc.gnu.org Subject: RE: GSoC Separate Host Process Offloadin

Re: Re: GSoC: want to take part in `Extend the static analysis pass for CPython Extension`

Hello, On Mon, Apr 03 2023, Eric Feng via Gcc wrote: > Hi Steven, > > I’m happy to collaborate on this project together — it would be great > to have your experience with CPython internals on the team. > While I normally welcome collaboration, please note that GSoC rules and reasonable caution di

Re: Re: GSoC: want to take part in `Extend the static analysis pass for CPython Extension`

Hi Steven, I’m happy to collaborate on this project together — it would be great to have your experience with CPython internals on the team. > And by the way, I can get to work long before the start-coding time point of > GSoC timeline. I can be involved in some capacity before the start-codin

Re: [GSoC] Interest and initial proposal for project on reimplementing cpychecker as -fanalyzer plugin

Thanks for bringing this to my attention Dave! I’m happy to collaborate on this project with Steven. I will reply in more detail in the other thread. Best, Eric On Sun, Apr 2, 2023 at 7:28 PM David Malcolm wrote: > > On Sat, 2023-04-01 at 19:49 -0400, Eric Feng wrote: > > > For the task above,

Re: GSoC: want to take part in `Extend the static analysis pass for CPython Extension`

ogsal/cpython/pull/63 I will submit a proposal on (b) as soon as possible. And by the way, I can get to work long before the start-coding timepoint of GSoC timeline. From: David Malcolm Sent: Monday, April 3, 2023 7:41 To: Sun Steven ; gcc@gcc.gnu.org Subject: Re:

Re: [GSoC][Static Analyzer] First proposal draft and a few more questions/requests

Hi Dave, > Overall, it looks great. Some notes: > - maybe specify the *GCC* static analyzer you first mention it Done. > - you talk about "timeout" warnings. The analyzer already can emit a > "timeout" warning of sorts, via -Wanalyzer-too-complex, though this is > based on the complexity of th

Re: GSoC: want to take part in `Extend the static analysis pass for CPython Extension`

On Sat, 2023-04-01 at 20:32 +, Sun Steven via Gcc wrote: > Hello, Hi! I just replied to your other email in the "[GSoC] Interest and initial proposal for project on reimplementing cpychecker as -fanalyzer plugin " thread. > > I want to take part in this project. > > b. Write a plugin to ad

Re: [GSoC] Interest and initial proposal for project on reimplementing cpychecker as -fanalyzer plugin

On Sat, 2023-04-01 at 19:49 -0400, Eric Feng wrote: > > For the task above, I think it's almost all there, it's "just" a > > case > > of implementing the special-case knowledge about the CPython API, > > mostly via known_function subclasses. > > Sounds good. > > > > In cpychecker I added some cu

Re: [GSoC] Interest and initial proposal for project on reimplementing cpychecker as -fanalyzer plugin

On Sun, 2023-04-02 at 17:24 +, Sun Steven via Gcc wrote: > Hi, Eric, Malcom, Hi - and welcome to the GCC community. > > Sorry that I didn't check this thread before. > > It sounds like there are a lot of things to do. I want to offer some > help. > > Let me add some backgrounds of memory m

Re: [GSoC][Static Analyzer] First proposal draft and a few more questions/requests

On Sat, 2023-04-01 at 16:19 +0200, Shengyu Huang wrote: > Hi Dave, > > > > > > > I has looked into compiling those files with the patch some time > > > ago; > > > looking at my notes, one issue was with this on-stack buffer: > > >    char extra[1024]; > > > declared outside the loop.  Inside the

Re: [GSoC][analyzer-c++] Enable enough C++ support for self-analysis

On Sat, 2023-04-01 at 01:33 +0200, Benjamin Priour wrote: > Hi David, > > > On Thu, Mar 30, 2023 at 2:04 AM David Malcolm > wrote: > > I think working on the C++ enablement prerequisites in the analyzer > > would make more sense.  I'd planned to do this myself for GCC 14, > > but > > there are p

Re: [GSoC] Interest and initial proposal for project on reimplementing cpychecker as -fanalyzer plugin

Hi, Eric, Malcom, Sorry that I didn't check this thread before. It sounds like there are a lot of things to do. I want to offer some help. Let me add some backgrounds of memory management in python here. ## Intro (for people unfamiliar with CPython) Unlike programs written in C++, where the c

Re: [GSoC] Interest and initial proposal for project on reimplementing cpychecker as -fanalyzer plugin

> For the task above, I think it's almost all there, it's "just" a case > of implementing the special-case knowledge about the CPython API, > mostly via known_function subclasses. Sounds good. > In cpychecker I added some custom function attributes: > https://gcc-python-plugin.readthedocs.io/e

Re: [GSoC][Static Analyzer] First proposal draft and a few more questions/requests

Hi Dave, >> >> I has looked into compiling those files with the patch some time ago; >> looking at my notes, one issue was with this on-stack buffer: >>char extra[1024]; >> declared outside the loop. Inside the loop, it gets modified in >> various ways: >>extra[0] = '\0'; >> and >>if

RE: GSoC Separate Host Process Offloading

he web but none specific to GCC). Thanks, Adi > -Original Message- > From: Prasad, Adi > Sent: Saturday, April 1, 2023 4:16 AM > To: 'Tobias Burnus' ; Thomas Schwinge > > Cc: gcc@gcc.gnu.org > Subject: RE: GSoC Separate Host Process Offloading > > Hi

RE: GSoC Separate Host Process Offloading

Hi Tobias, Thanks for the reply! > > Note that multiple offload targets are possible. For instance, on > Debian/Ubuntu, 'gcc -v' shows: > 'OFFLOAD_TARGET_NAMES=nvptx-none:amdgcn-amdhsa' and lto-wrapper then > cycles through those, finding the offloading compiler in > $PATH/accel//mkoffload > > E

Re: GSoC Separate Host Process Offloading

Hi Adi, On 31.03.23 14:35, Prasad, Adi wrote: Rework lto-wrapper so that if the separate host process target is enabled, it finds and calls a mkoffload for the host architecture instead of looking for an offloading compiler’s mkoffload; then write a mkoffload tool for a separate host process.

Re: GSoC Separate Host Process Offloading

, Adi Cc: gcc@gcc.gnu.org ; Tobias Burnus Subject: Re: GSoC Separate Host Process Offloading *** This email originates from outside Imperial. Do not click on links and attachments unless you recognise the sender. If you trust the sender, add them to your safe senders list https

Re: [GSOC] query about C++: Implement compiler built-in traits for the standard library traits

Hello, my apologies for a very late reply, unfortunately we have had an unpleasant hiccup in our internal miscommunication. On Thu, Mar 23 2023, Anastasia3412 wrote: > Thanks, Martin and Jonathan for your suggestion. I have already finished > building gcc from source. I was looking at other proj

Re: [GSoC] Conflicted Built-in Trait Name

I see. Thank you for the clarification! On Thu, Mar 30, 2023 at 5:23 AM Jonathan Wakely wrote: > > On Thu, 30 Mar 2023 at 09:33, Ken Matsui wrote: > > > > Hi François, > > > > On Wed, Mar 29, 2023 at 10:11 PM François Dumont > > wrote: > > > > > > Hi > > > > > > Do not hesitate to dig into libr

Re: [GSoC] Conflicted Built-in Trait Name

On Thu, 30 Mar 2023 at 09:33, Ken Matsui wrote: > > Hi François, > > On Wed, Mar 29, 2023 at 10:11 PM François Dumont wrote: > > > > Hi > > > > Do not hesitate to dig into library doc. Especially this page: > > > > https://gcc.gnu.org/onlinedocs/gcc-8.1.0/libstdc++/manual/manual/test.html > > > >

Re: [GSoC] Conflicted Built-in Trait Name

Hi François, On Wed, Mar 29, 2023 at 10:11 PM François Dumont wrote: > > Hi > > Do not hesitate to dig into library doc. Especially this page: > > https://gcc.gnu.org/onlinedocs/gcc-8.1.0/libstdc++/manual/manual/test.html > > You can also find it in your git clone in /libstdc++-v3/doc/html. > > Y

Re: [GSoC] Conflicted Built-in Trait Name

Hi Do not hesitate to dig into library doc. Especially this page: https://gcc.gnu.org/onlinedocs/gcc-8.1.0/libstdc++/manual/manual/test.html You can also find it in your git clone in /libstdc++-v3/doc/html. You'll see also how to run test in different std modes like --std=c++98 to catch the k

Re: [GSoC] A bunch of questions about sm-malloc behavior, and proposition of a GSoC subject.

On Thu, 2023-03-30 at 00:50 +0200, Benjamin Priour wrote: > Hi David, > > I've been playing around with sm-malloc on C++ samples. Note that the analyzer doesn't properly work yet on C++; see: https://gcc.gnu.org/bugzilla/showdependencytree.cgi?id=97110 I'm hoping to address much of this in GCC

Re: GSoC Separate Host Process Offloading

Hi Adi! On 2023-03-28T20:39:04+, "Prasad, Adi via Gcc" wrote: > I’m Adi Prasad, a 2nd year Computing student at Imperial College London, > interested in doing the Separate Host Process Offloading GSoC project this > summer. Greak, and welcome to GCC! :-) > First off, I’m aware I’m gettin

Re: GSoC Project - Bypass Assembler for LTO Object Files

Hello, we are delighted you found contributing to GCC interesting. On Tue, Mar 28 2023, Hathik H via Gcc wrote: > Dear Jan Hubicka, > > My name is Hathik , and I'm a student . I'm writing to express my interest > in the GCC LTO , and to ask for your guidance as I prepare my application. > > I hav

Re: GSoC Rust : Metadata exports for Rust frontend

Hello, we are delighted you found contributing to GCC interesting. On Mon, Mar 27 2023, Omkar Mohanty via Gcc wrote: > Hello GCC developers, > > I am Omkar Mohanty, currently an undergrad in CS. I have contributed to a > number of open Source organizations for the past one year and I have one > y

Re: GSoC 2023

Hello, we are delighted you found contributing to GCC interesting. On Mon, Mar 27 2023, Igor Putovny via Gcc wrote: > Dear all, > > I am a student of computer science and I was thinking about applying for > Google Summer of Code 2023. Naturally, I wanted to reach out to you before > applying for

Re: [GSoC] Conflicted Built-in Trait Name

Oooh, thank you for your help! On Tue, Mar 28, 2023 at 4:25 PM Jonathan Wakely wrote: > > On Tue, 28 Mar 2023 at 22:30, Ken Matsui via Libstdc++ > wrote: > > > > Hi François, > > > > I tried to use `make check-debug`, but my Makefile does not include > > the target. Could you please tell me how

Re: [GSoC] Conflicted Built-in Trait Name

On Tue, 28 Mar 2023 at 22:30, Ken Matsui via Libstdc++ wrote: > > Hi François, > > I tried to use `make check-debug`, but my Makefile does not include > the target. Could you please tell me how you generated your Makefile? It's a target in the libstdc++ makefile, so you need to run it from the $t

Re: [GSoC] Discussion of warnings and of a first patch (name-hiding)

Hello, it feels like I have read only a small part of your conversation and so may be missing quite some context, but... On Wed, Mar 22 2023, Benjamin Priour via Gcc wrote: > Hi Jason, > > Sorry for the delayed answer, I was in my exam period! > > I've almost finished the patch (PR12341 >

Re: [GSoC] Conflicted Built-in Trait Name

Hi François, I tried to use `make check-debug`, but my Makefile does not include the target. Could you please tell me how you generated your Makefile? FYI, I did this command: `../configure --enable-languages=c++ --disable-error --disable-bootstrap`. Sincerely, Ken Matsui On Mon, Mar 27, 2023 a

Re: [GSoC] Interest and initial proposal for project on reimplementing cpychecker as -fanalyzer plugin

On Tue, 2023-03-28 at 08:08 -0400, Eric Feng wrote: > My apologies. Forgot to CC the mailing list in my previous e-mail. > Original reply below: > > ___ > > > Hi David, > > Thank you for your feedback! > > > [...snip...] > > > > > > Error-handling checking: Various checks for common er

Re: [GSoC] Interest and initial proposal for project on reimplementing cpychecker as -fanalyzer plugin

My apologies. Forgot to CC the mailing list in my previous e-mail. Original reply below: ___ Hi David, Thank you for your feedback! > Also, the Python community would continue to find > static analysis of CPython extension modules useful, so it would be > good to have the idea live on as a

Re: [GSoC] Conflicted Built-in Trait Name

Jacobson's email was treated as spam somehow. Sorry for missing your email. On Mon, Mar 27, 2023 at 2:59 PM Jonathan Wakely wrote: > > On Sat, 25 Mar 2023 at 12:23, Roy Jacobson via Libstdc++ > wrote: > > > > Clang has been providing __is_void for a very long time now, and is > > definitely comp

Re: [GSoC] Conflicted Built-in Trait Name

On Sat, 25 Mar 2023 at 12:23, Roy Jacobson via Libstdc++ wrote: > > Clang has been providing __is_void for a very long time now, and is > definitely compatible with libstdc++. Does defining this builtin cause a > problem? Might be that the lookup rules for builtins are different or > something. >

Re: [GSoC] Conflicted Built-in Trait Name

Oh! Thank you! On Mon, Mar 27, 2023 at 2:49 PM Jonathan Wakely wrote: > > On Mon, 27 Mar 2023 at 22:43, Jonathan Wakely wrote: > > > > On Mon, 27 Mar 2023 at 21:17, Ken Matsui via Libstdc++ > > wrote: > > > > > > On Mon, Mar 27, 2023 at 10:33 AM François Dumont > > > wrote: > > > > > > > > >

Re: [GSoC] Conflicted Built-in Trait Name

On Mon, 27 Mar 2023 at 22:43, Jonathan Wakely wrote: > > On Mon, 27 Mar 2023 at 21:17, Ken Matsui via Libstdc++ > wrote: > > > > On Mon, Mar 27, 2023 at 10:33 AM François Dumont > > wrote: > > > > > > > > > On 26/03/2023 04:01, Ken Matsui via Libstdc++ wrote: > > > > On Sat, Mar 25, 2023 at 5:3

Re: [GSoC] Conflicted Built-in Trait Name

On Mon, 27 Mar 2023 at 21:17, Ken Matsui via Libstdc++ wrote: > > On Mon, Mar 27, 2023 at 10:33 AM François Dumont wrote: > > > > > > On 26/03/2023 04:01, Ken Matsui via Libstdc++ wrote: > > > On Sat, Mar 25, 2023 at 5:38 AM Marc Glisse wrote: > > >> On Sat, 25 Mar 2023, Ken Matsui via Gcc wrote

Re: [GSoC] Conflicted Built-in Trait Name

On Mon, Mar 27, 2023 at 10:33 AM François Dumont wrote: > > > On 26/03/2023 04:01, Ken Matsui via Libstdc++ wrote: > > On Sat, Mar 25, 2023 at 5:38 AM Marc Glisse wrote: > >> On Sat, 25 Mar 2023, Ken Matsui via Gcc wrote: > >> > >>> Built-in trait naming simply adds two underscores (__) to the or

Re: [GSoC] Conflicted Built-in Trait Name

On 26/03/2023 04:01, Ken Matsui via Libstdc++ wrote: On Sat, Mar 25, 2023 at 5:38 AM Marc Glisse wrote: On Sat, 25 Mar 2023, Ken Matsui via Gcc wrote: Built-in trait naming simply adds two underscores (__) to the original trait name. However, the same names are already in use for some built

Re: [GSoC][Static Analyzer] First proposal draft and a few more questions/requests

Hi Dave, > On 26 Mar 2023, at 19:14, David Malcolm wrote: > > I has looked into compiling those files with the patch some time ago; > looking at my notes, one issue was with this on-stack buffer: >char extra[1024]; > declared outside the loop. Inside the loop, it gets modified in > various

Re: [GSoC][Static Analyzer] First proposal draft and a few more questions/requests

On Sun, 2023-03-26 at 18:03 +0200, Shengyu Huang wrote: > Hi Dave, > > (I forgot to cc the list in the last email and it was too late to > unsend. Sorry for sending you the same email again.) > > > On 20 Mar 2023, at 23:50, David Malcolm > > mailto:dmalc...@redhat.com>> wrote: > > > > I think if

Re: [GSoC][Static Analyzer] First proposal draft and a few more questions/requests

Hi Dave, (I forgot to cc the list in the last email and it was too late to unsend. Sorry for sending you the same email again.) > On 20 Mar 2023, at 23:50, David Malcolm > wrote: > > I think if you try the patch to sm.cc above, then you'll see > vari

  1   2   3   4   5   6   7   8   9   >