https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97205
--- Comment #24 from rguenther at suse dot de <rguenther at suse dot de> --- On Thu, 20 May 2021, sripar01 at gcc dot gnu.org wrote: > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97205 > > --- Comment #23 from SRINATH PARVATHANENI <sripar01 at gcc dot gnu.org> --- > (In reply to rguent...@suse.de from comment #22) > > On Wed, 19 May 2021, bernd.edlinger at hotmail dot de wrote: > > > > > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97205 > > > > > > --- Comment #21 from Bernd Edlinger <bernd.edlinger at hotmail dot de> --- > > > Hi Srinath, > > > > > > when we add new assertions to gcc we use always a gcc_checking_assert > > > nowadays, that is also the case here. > > > > > > The assertion is only firing in your compiler because it is a development > > > snapshot 10.3.1. So that is an experimemtal version. > > > > 10.3.1 is not an experimental version, so the assert should not fire > > there unless you configure with --enable-checking (which you might > > have done). > > Thanks rguent...@suse.de and Bernd Edlinger. > > My I'm again having confusion with the wording development/release/experiment > versions. > > All development versions checks for gcc_checking_assert whether > --enable-checking=yes or --enable-checking=no (eg: 10.3.1), but release > versions only check for gcc_checking_assert when --enable-checking=yes > (eg:10.3.0). No. gcc_checking_assert is enabled when --enable-checking=yes --enable-checking defaults to =yes on the master branch. On release branches it defaults to =release, that includes snapshots and thus 10.3.1. > If I wanted to build a toolchain using development version (eg:10.3.1) and for > this test to not to fail , I should either pass --enable-checking=no or apply > this patch (which was committed to trunk) on the top of gcc-10.3.1 source > code. > > Is my understanding correct? You don't need anything special for 10.3.1, that is not a development version. If you do not specify any --enable-checking at configure time the default is that the assert does not trigger and thus the ICE should not happen.
