From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 130660 invoked by alias); 15 Nov 2018 16:56:14 -0000 Mailing-List: contact gcc-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-owner@gcc.gnu.org Received: (qmail 130201 invoked by uid 89); 15 Nov 2018 16:56:14 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-0.9 required=5.0 tests=BAYES_00,KAM_LAZY_DOMAIN_SECURITY,SPF_HELO_PASS autolearn=no version=3.3.2 spammy=Hx-languages-length:908 X-HELO: mx1.redhat.com Received: from mx1.redhat.com (HELO mx1.redhat.com) (209.132.183.28) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Thu, 15 Nov 2018 16:56:13 +0000 Received: from smtp.corp.redhat.com (int-mx05.intmail.prod.int.phx2.redhat.com [10.5.11.15]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id CAF8C30C6D79; Thu, 15 Nov 2018 16:56:11 +0000 (UTC) Received: from localhost.localdomain (ovpn-112-27.rdu2.redhat.com [10.10.112.27]) by smtp.corp.redhat.com (Postfix) with ESMTP id 547A85D738; Thu, 15 Nov 2018 16:56:10 +0000 (UTC) Subject: Re: Parallelize the compilation using Threads To: Richard Biener , Giuliano Augusto Faulin Belinassi Cc: GCC Development , kernel-usp@googlegroups.com, gold@ime.usp.br, alfredo.goldman@gmail.com References: From: Jeff Law Openpgp: preference=signencrypt Message-ID: Date: Thu, 15 Nov 2018 18:07:00 -0000 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.3.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-IsSubscribed: yes X-SW-Source: 2018-11/txt/msg00081.txt.bz2 On 11/15/18 3:29 AM, Richard Biener wrote: > >> 2. Did I correctly understand the goal of the parallelization? Can >> anyone provide extra details to me? > > You may want to search the mailing list archives since we had a > student application (later revoked) for the task with some discussion. > > In my view (I proposed the thing) the most interesting parts are > getting GCCs global state documented and reduced. The parallelization > itself is an interesting experiment but whether there will be any > substantial improvement for builds that can already benefit from make > parallelism remains a question. Agreed. Driving down the amount of global state is good in and of itself. It's also a prerequisite for parallelizing GCC itself using threads. I suspect driving down global state probably isn't that interesting for a master's thesis though :-) jeff