Thanks, David and Martin, for the heads up, and I am sorry for the late reply due to health issues. Anyways I could emit the warning "hello world, I am function foo.". After that, I tried debugging using the` ../gcc -wrapper gdb test.c`(gcc binary is in parent folder) but I am getting this error "gdb: unrecognized option '-dumpdir' Use `gdb --help' for a complete list of options.". I googled it and got this on Bugzilla (https://gcc.gnu.org/bugzilla/show_bug.cgi?id=53195), but it has already been fixed. These are the gdb configurations during the build: Using built-in specs. COLLECT_GCC=../gcc COLLECT_LTO_WRAPPER=gcc-dir/libexec/gcc/x86_64-pc-linux-gnu/12.2.1/lto-wrapper Target: x86_64-pc-linux-gnu Configured with: ../project/configure --prefix=gcc-dir --enable-languages=c,c++ --disable-bootstrap Thread model: posix Supported LTO compression algorithms: zlib zstd gcc version 12.2.1 20230302 [OG12] (GCC) COLLECT_GCC_OPTIONS='-v' '-mtune=generic' '-march=x86-64' '-dumpdir' 'a-' Can anyone point out how to resolve this or if I am missing something during build? Thanks and regards Rishi Raj On Tue, 7 Mar 2023 at 17:30, wrote: > Send Gcc mailing list submissions to > gcc@gcc.gnu.org > > To subscribe or unsubscribe via the World Wide Web, visit > https://gcc.gnu.org/mailman/listinfo/gcc > or, via email, send a message with subject or body 'help' to > gcc-request@gcc.gnu.org > > You can reach the person managing the list at > gcc-owner@gcc.gnu.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of Gcc digest..." > Today's Topics: > > 1. Re: [GSOC] Looking for small patch/project to work on > (David Malcolm) > 2. Re: Request for participation in GSoC (David Malcolm) > 3. Re: [GSoC] Introduction and query on LTO object emmission > project (David Malcolm) > 4. Clarification on newlib version for building AMDGCN > offloading backend (Wileam Yonatan Phan) > > > > ---------- Forwarded message ---------- > From: David Malcolm > To: Rishi Raj , gcc@gcc.gnu.org > Cc: > Bcc: > Date: Mon, 06 Mar 2023 11:25:16 -0500 > Subject: Re: [GSOC] Looking for small patch/project to work on > On Sat, 2023-03-04 at 08:11 +0530, Rishi Raj via Gcc wrote: > > Hi everyone, > > Hi, and welcome! > > > > > My name is Rishi Raj, and I am a third-year undergraduate studying > > Computer > > Science and Engineering at the Indian Institute of Technology > > Kharagpur in > > India. I wish to participate in this year's GSOC with GCC. > > > > My progress so far: > > > > 1. Successfully built the GCC from source using the installing gcc > > guide. (I will run the test suite today.) > > 2. Read about different configuration options during installations > > and > > also went through the gcc-newbies-guide, which was an exciting > > read and > > provided an overview of how to proceed in gcc-contribution. I want > > to > > extend my appreciation to David for this. > > Thanks. You've already built GCC from source, which is a great start. > A good thing to try next (if you haven't already) would be to try > hacking in a warning that emits: > "hello world, I'm compiling function 'foo'" > for each function being compiled, and compile something with that... > and then do it again in the debugger, with a breakpoint on that, and > step through some of the code, as per: > > https://gcc-newbies-guide.readthedocs.io/en/latest/getting-started.html#hello-world-from-the-compiler > > The point here is to get you and your development environment to the > point where you can comfortably make a simple change to GCC's source, > rebuild it and quickly see the results of your edits (without having to > wait ages), and for you to get comfortable stepping through it in the > debugger. > > Let me know if you run into issues (which could suggest improvements to > the guide). > > > > > After reading about the suggested projects described on GCC's GSOC > > page, I > > found "Bypass assembler when generating LTO object files" and "C++: > > Implement compiler built-in traits for the standard library traits" > > interesting. Currently, I am examining the preliminary patch > > https://gcc.gnu.org/ml/gcc/2014-09/msg00340.html for the first > > project. > > FWIW I'm not particularly expert at the specific areas of GCC relating > to the two projects you mentioned, so hopefully others on this list can > give advice/mentoring with those. > > > I > > can work on a small project/patch after this in a day or two. I would > > greatly appreciate your suggestions for the same. > > I'm biased here in favor of my own subproject, the static analyzer; as > discussed in the recent "[GSoC][Static Analyzer] Ideas for proposal" > thread on this list there are dozens of RFEs against the "analyzer" > component in our bugzilla, many of which are relatively small. That > said analyzer is quite complicated, so I don't know if that's a good > first warm-up for someone who isn't planning to work on the analyzer > for their GSoC project. > > We have an "easyhack" keyword in our bugzilla which you could try > searching on that. Unfortunately, people's definitions of what is easy > vary, and I don't think anyone's been curating that list recently, so > you might want to check in here with the URLs of the things that catch > your eye to make sure they're reasonable first projects. > > > > > I have taken compiler theory and laboratory courses as a part of my > > institute curriculum. In the laboratory, we designed a tiny-c > > compiler (a > > subset of GCC). In theory, I learned about different phases of > > compilations, various optimization techniques, etc. > > > > Please find my course website link for a detailed overview: > > https://cse.iitkgp.ac.in/~bivasm/compiler2022.html#Lecture > > > > This course was the starting point of my interest in compiler > > development, > > and I want to take it further by making meaningful contributions to > > GCC. I > > hope to make some significant contributions to GCC this summer and in > > the > > future. I would appreciate any suggestions on taking on a small > > patch/project or delving deeper into the projects I am interested in > > pursuing. > > It sounds like you have a lot of relevant knowledge; I hope we can find > you something you'll enjoy working on. > > Let me know if you have any questions > > Hope this is helpful; welcome again. > Dave > > > > > > ---------- Forwarded message ---------- > From: David Malcolm > To: Priyabrata Mondal , gcc@gcc.gnu.org > Cc: > Bcc: > Date: Mon, 06 Mar 2023 11:29:28 -0500 > Subject: Re: Request for participation in GSoC > On Sat, 2023-03-04 at 20:56 +0530, Priyabrata Mondal via Gcc wrote: > > Respected sir, > > I am Priyabrata Mondal, an M.tech student in Electric > > Transportation at the Indian Institute of Technology(IIT), Mandi. I > > want to > > participate in Google Summer of Code 2023 by contributing to the > > *Fortran – > > DO CONCURRENT* project, an implementation of loop that executes > > concurrently. I have started to learn about parallel programming and > > Fortran programming language. > > I have good knowledge of C, C++, Javascript, HTML, and > > CSS. > > can you suggest some resources so I can learn the > > technologies > > that are required for this project? > > I will be highly grateful to you forever if you allow me > > to do > > this project under your guidance. > > Hello, welcome to the GCC community. > > If you haven't seen it already, I've written a guide aimed at new GCC > developers here: > https://gcc-newbies-guide.readthedocs.io/en/latest/index.html > > A good first step would be to try to build gcc from source, add a > simple warning that emits: > "hello world, I'm compiling function 'foo'" > for each function being compiled, and compile something with that... > and then do that again, stepping through it in the debugger. There are > instructions about that in the guide above. > > Hope this is helpful > Dave > > > > > > ---------- Forwarded message ---------- > From: David Malcolm > To: Jan Hubicka , Peter Lafreniere > Cc: GCC > Bcc: > Date: Mon, 06 Mar 2023 11:48:14 -0500 > Subject: Re: [GSoC] Introduction and query on LTO object emmission project > On Fri, 2023-03-03 at 19:28 +0100, Jan Hubicka via Gcc wrote: > > Hello, > > > Hi! I've been interested in compiler development for a while, and > > > would love to > > > work with any of you as part of GSoC, or even just as a side- > > > project on my own. > > > > > > I'm an 18 year-old student going into university next year with a > > > passion for all > > > things open source and low level. I consider myself fluent in c, > > > and proficient > > > with c++, rust, and x86 assembly, but unfamiliar with practical > > > compiler design. > > > I have done some reading on the theoretical aspects of compilers, > > > however. > > Hi Peter > > BTW, in case you haven't seen it, I've written a guide aimed at new GCC > contributors here: > https://gcc-newbies-guide.readthedocs.io/en/latest/index.html > > A good first step would be to try to build gcc from source, add try > adding a simple warning that emits: > "hello world, I'm compiling function 'foo'" > for each function being compiled, and compile something with that... > then try stepping through cc1 doing that in the debugger. There are > instructions about that in the guide above. > > Hope this is helpful > Dave > > > > > > ---------- Forwarded message ---------- > From: Wileam Yonatan Phan > To: "gcc@gcc.gnu.org" > Cc: > Bcc: > Date: Mon, 6 Mar 2023 19:23:50 +0000 > Subject: Clarification on newlib version for building AMDGCN offloading > backend > Hi, > > I'm working on adding a build recipe for GCC with AMDGCN offloading > backend in Spack. Can anyone clarify the following sentence listed on the > wiki? > > >The Newlib version needs to be contemporaeous with GCC, at least until > the ABI is finalized. > < > https://gcc.gnu.org/wiki/Offloading#How_to_build_an_offloading-enabled_GCC > > > > What are the correct contemporaneous versions for each version of GCC >= > 10? > > Thanks, > Wil > >