Re: Help with an arm64 specific gcc internal error with polymake

2020-12-01 Thread Adrian Bunk
On Fri, Nov 27, 2020 at 06:52:05AM -0400, David Bremner wrote: > Wookey writes: > > > On 2020-11-17 21:19 +, Dominic Hargreaves wrote: > >> Thanks for your work on this. As of today polymake has been uploaded > >> to use gcc-9 which doesn't have this problem, so the perl transition > >> has

Re: Help with an arm64 specific gcc internal error with polymake

2020-11-27 Thread David Bremner
Wookey writes: > On 2020-11-17 21:19 +, Dominic Hargreaves wrote: >> Thanks for your work on this. As of today polymake has been uploaded >> to use gcc-9 which doesn't have this problem, so the perl transition >> has been unblocked. > > I don't understand how this works, because Alex was

Re: Help with an arm64 specific gcc internal error with polymake

2020-11-26 Thread Wookey
On 2020-11-17 21:19 +, Dominic Hargreaves wrote: > Thanks for your work on this. As of today polymake has been uploaded > to use gcc-9 which doesn't have this problem, so the perl transition > has been unblocked. I don't understand how this works, because Alex was able to reproduce the all

Re: Help with an arm64 specific gcc internal error with polymake

2020-11-17 Thread Wookey
On 2020-11-17 20:11 -0400, David Bremner wrote: > Dominic Hargreaves writes: > > Thanks for your work on this. As of today polymake has been uploaded > > to use gcc-9 which doesn't have this problem, so the perl transition > > has been unblocked. Good plan. > I don't forsee having time (or

Re: Help with an arm64 specific gcc internal error with polymake

2020-11-17 Thread David Bremner
Dominic Hargreaves writes: > On Sun, Nov 15, 2020 at 01:49:23AM +, Wookey wrote: >> On 2020-11-14 16:33 +, Dominic Hargreaves wrote: >> > On Sat, Nov 14, 2020 at 03:08:14PM +, Wookey wrote: >> >> > > I have just tried it, and the file built OK, getting to a resident >> > > footprint

Re: Help with an arm64 specific gcc internal error with polymake

2020-11-17 Thread Dominic Hargreaves
On Sun, Nov 15, 2020 at 01:49:23AM +, Wookey wrote: > On 2020-11-14 16:33 +, Dominic Hargreaves wrote: > > On Sat, Nov 14, 2020 at 03:08:14PM +, Wookey wrote: > > > > I have just tried it, and the file built OK, getting to a resident > > > footprint of about 3.5G before completing. >

Re: Help with an arm64 specific gcc internal error with polymake

2020-11-14 Thread Wookey
On 2020-11-14 16:33 +, Dominic Hargreaves wrote: > On Sat, Nov 14, 2020 at 03:08:14PM +, Wookey wrote: > > I have just tried it, and the file built OK, getting to a resident > > footprint of about 3.5G before completing. OK, reading the bug a bit more carefully, I see that you were

Re: Help with an arm64 specific gcc internal error with polymake

2020-11-14 Thread Christian Kastner
On 11/14/20 4:08 PM, Wookey wrote: > Yes. I have a 64Gb machine. (emag). I wasn't aware that the Ampere stuff was generally available, and now I see that through a generous donation, they power our buildds [1]. Do these run an unmodified Debian? I'd like to run my own arm64 buildd, but

Re: Help with an arm64 specific gcc internal error with polymake

2020-11-14 Thread Dominic Hargreaves
On Sat, Nov 14, 2020 at 03:08:14PM +, Wookey wrote: > On 2020-11-14 14:30 +, Dominic Hargreaves wrote: > > On Wed, Nov 11, 2020 at 10:12:19PM +, Dominic Hargreaves wrote: > > > During the perl 5.32 transition we observed a build failure on arm64 which > > > is reproducible on the

Re: Help with an arm64 specific gcc internal error with polymake

2020-11-14 Thread Wookey
On 2020-11-14 14:30 +, Dominic Hargreaves wrote: > On Wed, Nov 11, 2020 at 10:12:19PM +, Dominic Hargreaves wrote: > > During the perl 5.32 transition we observed a build failure on arm64 which > > is reproducible on the porterbox and at lease three different buidds:: > > > >

Re: Help with an arm64 specific gcc internal error with polymake

2020-11-14 Thread Dominic Hargreaves
On Wed, Nov 11, 2020 at 10:12:19PM +, Dominic Hargreaves wrote: > During the perl 5.32 transition we observed a build failure on arm64 which > is reproducible on the porterbox and at lease three different buidds:: > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=974073 > > However