From: Jeff Law <law@redhat.com>
To: Jim Wilson <jim.wilson@linaro.org>,
"gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] move check-gcc parallelize value into C front end
Date: Tue, 19 May 2015 06:48:00 -0000 [thread overview]
Message-ID: <555ADACA.9080405@redhat.com> (raw)
In-Reply-To: <CABXYE2WxkD8K0qqy0XPN12nmC8piqu0OD+QuWmL_6GK2AVTBZw@mail.gmail.com>
On 05/17/2015 09:42 PM, Jim Wilson wrote:
> Every check_$lang_parallelize setting is in the language specific
> Make-lang.in file except for the C front-end check_gcc_parallelize
> setting which is in the toplevel Makefile.in file. This seems to be
> an oversight, as it was only 3 years ago that the c/ subdir was
> created, and the check_gcc_parallelize variable looks like it might be
> gcc generic, but it is actually C front end specific as it only affect
> check-gcc which is a C front end target. This patch moves the
> variable into the C front end where it belongs. This also
> consolidates the change_$lang_parallelize docs, which are currently
> spread across two places. It also needs to fix two places that
> directly refer to the check_gcc_parallelize setting in Makefile.in,
> and change them to references to the generic docs.
>
> Also, while looking at this, I noticed that there is no
> check_gnat_parallelize set, and check-gnat seems to be the only
> testsuite target that hasn't already been parallelized. This also
> looks like an oversight, but I haven't tested a patch for that yet.
>
> Jim
>
>
> check-parallel.patch
>
>
> gcc/
> 2015-05-17 Jim Wilson<jim.wilson@linaro.org>
>
> * Makefile.in (check_gcc_parallelize): Delete.
> (lang_checks_parallelized): Update comment.
>
> gcc/c
> 2015-05-17 Jim Wilson <wilson@lothlorien>
>
> * Make-lang.in (check_gcc_pallelize): Define.
>
> gcc/cp
> 2015-05-17 Jim Wilson <wilson@lothlorien>
>
> * Make-lang.in (check_g++_parallelize): Update comment.
>
> gcc/fortran
> 2015-05-17 Jim Wilson <wilson@lothlorien>
>
> * Make-lang.in (check_gfortran_parallelize): Update comment.
OK.
jeff
prev parent reply other threads:[~2015-05-19 6:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-18 5:15 Jim Wilson
2015-05-19 6:48 ` Jeff Law [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=555ADACA.9080405@redhat.com \
--to=law@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jim.wilson@linaro.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).