RFC: Changing default ggc-min-expand on mips and mipsel?

2016-10-18 Thread Aurelien Jarno
Hi all, On mips and mipsel, we have more and more packages failing to build from source with a "virtual memory exhausted" error in GCC, due to the 2GB address space limit. It seems the occurrence is even higher since the switch to GCC 6. The usual answer has been to play with the ggc-min-expand

Re: RFC: Changing default ggc-min-expand on mips and mipsel?

2016-10-18 Thread James Cowgill
Hi, On 18/10/16 13:49, Aurelien Jarno wrote: > On mips and mipsel, we have more and more packages failing to build from > source with a "virtual memory exhausted" error in GCC, due to the 2GB > address space limit. It seems the occurrence is even higher since the > switch to GCC 6. The usual

Re: RFC: Changing default ggc-min-expand on mips and mipsel?

2016-10-18 Thread Aurelien Jarno
On 2016-10-18 15:04, James Cowgill wrote: > Hi, > > On 18/10/16 13:49, Aurelien Jarno wrote: > > On mips and mipsel, we have more and more packages failing to build from > > source with a "virtual memory exhausted" error in GCC, due to the 2GB > > address space limit. It seems the occurrence is