From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.5-pre1 (2020-06-20) on
	ip-172-31-74-118.ec2.internal
X-Spam-Level: 
X-Spam-Status: No, score=0.0 required=3.0 tests=BAYES_40,FREEMAIL_FROM
	autolearn=ham autolearn_force=no version=3.4.5-pre1
X-Received: by 2002:a37:596:: with SMTP id 144mr8050884qkf.387.1614927202476;
        Thu, 04 Mar 2021 22:53:22 -0800 (PST)
X-Received: by 2002:a25:240f:: with SMTP id k15mr11023649ybk.363.1614927202084;
 Thu, 04 Mar 2021 22:53:22 -0800 (PST)
Path: eternal-september.org!reader02.eternal-september.org!news.mixmin.net!proxad.net!feeder1-2.proxad.net!209.85.160.216.MISMATCH!news-out.google.com!nntp.google.com!postnews.google.com!google-groups.googlegroups.com!not-for-mail
Newsgroups: comp.lang.ada
Date: Thu, 4 Mar 2021 22:53:21 -0800 (PST)
In-Reply-To: <lyczweh6pd.fsf@pushface.org>
Injection-Info: google-groups.googlegroups.com; posting-host=87.88.29.208; posting-account=6yLzewoAAABoisbSsCJH1SPMc9UrfXBH
NNTP-Posting-Host: 87.88.29.208
References: <602e608e$0$27680$e4fe514c@news.kpn.nl> <60379b69$0$20345$e4fe514c@news.kpn.nl>
 <s1a9jm$1c9e$1@gioia.aioe.org> <86zgzn4xcs.fsf@stephe-leake.org>
 <5b0c7577-7dcc-468b-a24b-7447a8e796b7n@googlegroups.com> <3808e6ec-1a49-4514-84e7-f444d94cdb2cn@googlegroups.com>
 <lyzgzlsyto.fsf_-_@pushface.org> <lyczweh6pd.fsf@pushface.org>
User-Agent: G2/1.0
MIME-Version: 1.0
Message-ID: <c5965fa4-4dd5-4808-be70-e9e6ee108f7dn@googlegroups.com>
Subject: Re: rr
From: Emmanuel Briot <briot.emmanuel@gmail.com>
Injection-Date: Fri, 05 Mar 2021 06:53:22 +0000
Content-Type: text/plain; charset="UTF-8"
Xref: reader02.eternal-september.org comp.lang.ada:61474
List-Id: <comp.lang.ada>

> > I doubt that posting on the GCC Bugzilla would get a speedy response
> In this case, it did[1]. Nothing like being able to provide a reproducer 
> (and having ICE, Internal Compiler Error, in the description may help 
> too). 

Even as a supported customer, it does help a lot when we can provide a small self-contained reproducer. Such bugs (including with "ICE" in the subject, we use the same trick :-) tend to be fixed pretty fast.
This is time consuming for compilation errors, but on the whole it takes one to two hours in general.
For run time issues (we currently have an optimization bug for instance), this is way more complex...