On 21. 01. 22 19:17, Jakub Jelinek wrote:
On Fri, Jan 21, 2022 at 07:10:53PM +0100, Miro Hrončok wrote:
On 21. 01. 22 19:07, Jakub Jelinek wrote:
On Fri, Jan 21, 2022 at 07:00:41PM +0100, Miro Hrončok wrote:
On 21. 01. 22 17:55, Jakub Jelinek wrote:
In all cases, if it is some compiler error
On Fri, 21 Jan 2022 19:10:53 +0100
Miro Hrončok wrote:
> On 21. 01. 22 19:07, Jakub Jelinek wrote:
> > On Fri, Jan 21, 2022 at 07:00:41PM +0100, Miro Hrončok wrote:
> >> On 21. 01. 22 17:55, Jakub Jelinek wrote:
> >>> In all cases, if it is some compiler error or internal compiler error,
> >>> pr
On Fri, Jan 21, 2022 at 07:10:53PM +0100, Miro Hrončok wrote:
> On 21. 01. 22 19:07, Jakub Jelinek wrote:
> > On Fri, Jan 21, 2022 at 07:00:41PM +0100, Miro Hrončok wrote:
> > > On 21. 01. 22 17:55, Jakub Jelinek wrote:
> > > > In all cases, if it is some compiler error or internal compiler error,
On 21. 01. 22 19:07, Jakub Jelinek wrote:
On Fri, Jan 21, 2022 at 07:00:41PM +0100, Miro Hrončok wrote:
On 21. 01. 22 17:55, Jakub Jelinek wrote:
In all cases, if it is some compiler error or internal compiler error,
preprocessed source + gcc command line would be highly appreciated,
having us
On Fri, Jan 21, 2022 at 07:00:41PM +0100, Miro Hrončok wrote:
> On 21. 01. 22 17:55, Jakub Jelinek wrote:
> > In all cases, if it is some compiler error or internal compiler error,
> > preprocessed source + gcc command line would be highly appreciated,
> > having us to try to rebuild all the packag
On 21. 01. 22 17:55, Jakub Jelinek wrote:
In all cases, if it is some compiler error or internal compiler error,
preprocessed source + gcc command line would be highly appreciated,
having us to try to rebuild all the packages again and dig those up
will be very time consuming.
But I suppose you
Hi!
There have been way too many mails recently in the
gcc-12.0.0-0.4.fc36 in rawhide thread and separate threads,
so for those which we haven't responded to yet or new issues,
can I ask you to track it in bugzilla instead of mailing list?
For issues where you suspect it is a bug on a package sid