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 -
>
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
Snapshot gcc-13-20240330 is now available on
https://gcc.gnu.org/pub/gcc/snapshots/13-20240330/
and on various mirrors, see https://gcc.gnu.org/mirrors.html for details.
This snapshot has been generated from the GCC 13 git branch
with the following options: git://gcc.gnu.org/git/gcc.git branch
Hello,
On Wed, Mar 27 2024, Soumya Ranjan wrote:
> Hello!
> Thanks for your response Martin!
> Sorry for the late response, I've been researching the project, going over
> the source code and preparing the proposal. After a lot of thought, I've
> decided to go with the "Offloading to a separate pr
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
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
On 2024-03-15 10:25, Tom Tromey wrote:
> gdb used to use a mish-mash of different approaches, some quite strange,
> but over the last few years we standardized on Python scripts that
> generate files. They're written to be seamless -- just invoke in the
> source dir; the output is then just par
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
