Re: How to get started with Contribution
On Sat, Feb 19, 2022 at 2:45 AM Purvak Baliyan via Gcc wrote: > > Respected Sir/Madam > > I am Purvak Baliyan, an Information Technology undergrad, I have entered my > third year at DR. Akhilesh Das Gupta Institute of Technology & > Management(ADGITM). I am new to open source contributions but i am well > aware of C/C++, Data Structure and Algorithms, and HTML & CSS. I would love > to contribute to your organisation but could you please tell me how to get > started? > > Hoping to hear from you soon. Thanks for your interest in GCC. Welcome! A good place to start is the GCC Wiki Getting Started page: https://gcc.gnu.org/wiki/#Getting_Started_with_GCC_Development and browse other recent answers to similar questions in the archives of this mailing list. Thanks, David
Bisected failure
Hi My application running on a stm32f7 started to behave "random" when compiled with gcc 10.1 - Gcc 9.x works fine. By random I mean this. 1. Flash the application onto the target. 2. reset - the application starts up fine 2. reset again - the application somehow goes haywire during startup effectively starting over with out a reset. That ends up leaving interrups and timers enabled fireing during BSS clear. 3. Reset again - now the application starts up fine again. 4. reset again - lockup again 5. reset again - lockup again 6 ... I have bisected and verified that whatever makes my commit 79f1d8521882de51480866fd7037199d670316bd (HEAD, refs/bisect/bad) Author: Jan Hubicka Date: Thu Nov 14 14:30:46 2019 +0100 * params.opt (max-inline-insns-single-O2): Set to 70 (instead of 30). From-SVN: r278221 Do you have any ideas to how to hunt down this bug? Besides trying to isolate the place where things go wrong. I'm unsure if GCC does something that the hardware does not like or my application is buggy. In any case I'd like to figure out the root cause. I do not like to be stuck at gcc 9 because of these kinds of issues :) I'd appreciate any input you might have. /Søren
gcc-11-20220219 is now available
Snapshot gcc-11-20220219 is now available on https://gcc.gnu.org/pub/gcc/snapshots/11-20220219/ and on various mirrors, see http://gcc.gnu.org/mirrors.html for details. This snapshot has been generated from the GCC 11 git branch with the following options: git://gcc.gnu.org/git/gcc.git branch releases/gcc-11 revision 3eecfec27666b16b2ef855f32ba3f975e087dec1 You'll find: gcc-11-20220219.tar.xz Complete GCC SHA256=d9663e61efee5115c15f85343b182111e352c1dcaa91ea7b68908982ecd8a426 SHA1=7f67c92b915da4b9a97c6ed86aebd38a5f84e162 Diffs from 11-20220212 are available in the diffs/ subdirectory. When a particular snapshot is ready for public consumption the LATEST-11 link is updated and a message is sent to the gcc list. Please do not use a snapshot before it has been announced that way.
