Currently gcc_release builds GCC (for generating in-tree generated
files) serially - that's prohibitly expensive and takges ages (>4h for
me). I'm using (when I remember to edit gcc_release ...) -j6 without
a problem for some years, thus the following proposal.
Any recommendation for the defaul
On Mon, Jan 22, 2018 at 09:37:05AM +0100, Richard Biener wrote:
>
> Currently gcc_release builds GCC (for generating in-tree generated
> files) serially - that's prohibitly expensive and takges ages (>4h for
> me). I'm using (when I remember to edit gcc_release ...) -j6 without
> a problem for s
On 01/22/2018 01:57 AM, Jakub Jelinek wrote:
> On Mon, Jan 22, 2018 at 09:37:05AM +0100, Richard Biener wrote:
>>
>> Currently gcc_release builds GCC (for generating in-tree generated
>> files) serially - that's prohibitly expensive and takges ages (>4h for
>> me). I'm using (when I remember to e
On Mon, 22 Jan 2018, Jeff Law wrote:
> On 01/22/2018 01:57 AM, Jakub Jelinek wrote:
> > On Mon, Jan 22, 2018 at 09:37:05AM +0100, Richard Biener wrote:
> >>
> >> Currently gcc_release builds GCC (for generating in-tree generated
> >> files) serially - that's prohibitly expensive and takges ages (>