Hi Dave, Thank you for your message.
Yes, I am able to make changes to GCC, rebuild it, and step through the modified code using a debugger. I have already tested this workflow and confirmed that everything works as expected. Could you also briefly describe the project and how it will work technically? Best regards, Islom пн, 9 мар. 2026 г., 18:33 David Malcolm <[email protected]>: > On Sun, 2026-03-08 at 15:17 +0500, Islombek Ismoilov wrote: > > Hi Dave > > Thanks for the advise. I've the fixed the issue by performing clean > > build. > > I removed the old GCC source directory entirely, and re-downloaded > > the > > source, and reapplied my changes. It is working correctly now. > > Excellent. > > Are you able to make changes to gcc, rebuild it, and step through the > changed code in a debugger? That's a good prerequisite that we want to > get applicants to achieve. > > Dave > > > > > > best regards, > > Islom > > > > вс, 8 мар. 2026 г. в 05:32, David Malcolm <[email protected]>: > > > > > On Thu, 2026-03-05 at 00:10 +0100, Martin Jambor wrote: > > > > Hello Islombek, > > > > > > > > On Tue, Mar 03 2026, Islombek Ismoilov via Gcc wrote: > > > > > Dear David Malcolm > > > > > > > > > > I would like to share my progress on building and modifying the > > > > > GNU > > > > > compiler from source. > > > > > > > > > > I successfully built GCC from the source code. During the > > > > > process, > > > > > I > > > > > resolved dependency and configuration issues that arose. > > > > > > > > > > After the build was completed, I tested the compiled compiler > > > > > using > > > > > a > > > > > simple test.c file. > > > > > > > > > > int main(){ > > > > > > > > > > return 0; > > > > > > > > > > } > > > > > > > > > > The compilation and execution worked correctly, confirming that > > > > > the > > > > > build > > > > > was functioning as expected. > > > > > > > > > > Then I started experimenting with modifications in the source > > > > > code. > > > > > I > > > > > edited the file c-parser.cc , specifically the function > > > > > "c_parser_translation_unit" and added the following line: > > > > > > > > > > warning (0, "Good Job"); > > > > > > > > > > My goal was to introduce a warning that would appear during > > > > > each > > > > > compilation. > > > > > > > > When I want to check that a code gets executed in the most simple > > > > way, I > > > > just resort to fprintf. The trick is to direct the output to > > > > stderr. > > > > Putting > > > > > > > > fprintf (stderr, "Good job!\n"); > > > > > > > > at the beginning of c_parser_translation_unit does what you'd > > > > expect > > > > it > > > > to do. > > > > > > > > > > > > > > However, after making the changes and rebuilding, the cc1 > > > > > binary > > > > > was not > > > > > generated. The build process completes the configuration stage > > > > > but > > > > > fails to > > > > > produce the main compiler binary. I restored c-parser.cc to its > > > > > original > > > > > state, yet the issue still persists , the build still finishes > > > > > without > > > > > generating cc1. > > > > > > > > This is of course strange. What were the commands you issued (in > > > > which > > > > directories) and what were the error messages? There should be > > > > no > > > > need > > > > to re-run configuration after such small change. Did make exit > > > > with > > > > exit code zero? > > > > > > > > Did you disable bootstrap during the first configuration step? > > > > > > This is very important when preparing to make changes to GCC, > > > otherwise > > > making edits is very tedious. Islombek, did you check this? > > > > > > > > > > > > > > > > > what do you advise? > > > > > > > > I'm afraid we need more details, after you restore the file, all > > > > should > > > > be as before, of course. > > > > > > > > Good luck debugging this and with GSoC in general. > > > > > > Islombek: did you get any further with this, or are you stuck? > > > > > > Hope this is constructive > > > Dave > > > > > > > >
