Am Mittwoch, den 29.12.2021, 20:34 +0530 schrieb Nilesh Patra:
> On 12/29/21 6:31 PM, Martin Uecker wrote:
> > Am Mittwoch, den 29.12.2021, 11:06 +0100 schrieb Martin Uecker:
> > > Hi Nilesh,
> > ...
> >
> > > > - try to work around by patching? (would be easy
> > > > only with access to the
On 12/29/21 6:31 PM, Martin Uecker wrote:
Am Mittwoch, den 29.12.2021, 11:06 +0100 schrieb Martin Uecker:
Hi Nilesh,
...
- try to work around by patching? (would be easy
only with access to the affected architectures)
This would be best. You could try with qemu to emulate these archs.
Am Mittwoch, den 29.12.2021, 11:06 +0100 schrieb Martin Uecker:
> Hi Nilesh,
...
> > - try to work around by patching? (would be easy
> >only with access to the affected architectures)
> >
> > This would be best. You could try with qemu to emulate these archs.
>
> I guess this is what I
Hi Nilesh,
thanks!
> On 12/28/21 5:36 PM, Martin Uecker wrote:
>
> Hi all,
>
> this is caused by some compiler bug in GCC 11. Any advice how
> to proceed?
>
> - use GCC 11
(I meant GCC 10)
> If this really is a bug in the _compiler itself_, maybe simply
> file a bug report against gcc-11
On 12/28/21 5:36 PM, Martin Uecker wrote:
Hi all,
this is caused by some compiler bug in GCC 11. Any advice how
to proceed?
- use GCC 11
If this really is a bug in the _compiler itself_, maybe simply file a bug
report against gcc-11 itself?
Please do this regardless of the solution ^^
-
Hi all,
this is caused by some compiler bug in GCC 11. Any advice how
to proceed?
- use GCC 11
- exclude affected architectures?
- try to work around by patching? (would be easy
only with access to the affected architectures)
- talk to the release team?
Best,
Martin
6 matches
Mail list logo
