From: Jeff Law <law@redhat.com>
To: Andrew MacLeod <amacleod@redhat.com>,
gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: [patch] New remainder of front end header reduction
Date: Mon, 09 Nov 2015 21:33:00 -0000 [thread overview]
Message-ID: <5641113A.6050609@redhat.com> (raw)
In-Reply-To: <56376BED.2040804@redhat.com>
On 11/02/2015 06:58 AM, Andrew MacLeod wrote:
> On 11/02/2015 01:41 AM, Jeff Law wrote:
>> On 10/30/2015 07:37 AM, Andrew MacLeod wrote:
>>> OK, here's the much delayed front end reduction patch based on the
>>> reordering already being checked in.
>>>
>>> I discovered that my targets builds were only building c/c++, so the
>>> other languages were being reduced based only on the host
>>> x86_64-pc-linux-gnu build. Thats *probably* ok, but I wanted to be
>>> sure. This is when I discovered that the other languages have varying
>>> amounts of support amongst the targets. Simply building all the targets
>>> to compile, say ada, doesn't actually work quite right.
>>>
>>> So this patch covers all the languages which do have full support.. the
>>> ones enabled by 'all' languages.
>>>
>>> I am determining which targets build the other languages now, and will
>>> submit separate reduction patches for those languages.
>>>
> Here's the rest of the front end files. I will temporarily hold off
> checking in the other front end file due to the ENABLE_OFFLOADING and
> ENABLE_FOLD_CHECKING issues brought up. I'll rerun the tool with all
> the ENABLE_* macros I can fine predefined in the tool to avoid this
> issue, and adjust he front end patches if necessary.. ie, if the tool
> finds a reduction that shouldnt happen.
>
> Anyway, here's the rest of the header files which should be the final
> patch I ran the tool on the coverage components of config-list.mk that
> supported each of the languages, then did a full build of all targets.
>
> bootstraps on x86_64-pc-linux-gnu with no new regressions, and passes
> all of config-list.mk
The remaining header file removals are fine.
jeff
next prev parent reply other threads:[~2015-11-09 21:33 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-23 16:57 [patch] New backend " Andrew MacLeod
2015-10-23 19:25 ` Jeff Law
2015-10-30 18:03 ` Cesar Philippidis
2015-10-30 18:29 ` Andrew MacLeod
2015-10-30 20:24 ` Andrew MacLeod
2015-10-30 20:27 ` Cesar Philippidis
2015-10-30 20:52 ` Jeff Law
2015-10-30 20:54 ` cgraph offloading error? Nathan Sidwell
2015-10-30 21:04 ` Jeff Law
2015-10-30 21:22 ` Nathan Sidwell
2015-10-30 21:31 ` Jeff Law
2015-10-30 22:17 ` Nathan Sidwell
2015-10-30 22:31 ` Nathan Sidwell
2015-10-30 22:33 ` Jeff Law
2015-10-30 23:01 ` Nathan Sidwell
2015-10-30 22:16 ` [patch] New backend header reduction Jeff Law
2015-11-02 8:43 ` Offload configurations (was: [patch] New backend header reduction) Thomas Schwinge
2015-10-30 13:38 ` [patch] New 'all' front end header reduction Andrew MacLeod
2015-10-30 16:20 ` Mike Stump
2015-10-30 16:35 ` Andrew MacLeod
2015-10-30 16:39 ` Mike Stump
2015-11-02 6:41 ` Jeff Law
2015-11-02 13:58 ` [patch] New remainder of " Andrew MacLeod
2015-11-09 21:33 ` Jeff Law [this message]
2015-10-31 7:02 ` [patch] New backend " Andreas Schwab
2015-10-31 8:14 ` Markus Trippelsdorf
2015-10-31 15:24 ` Markus Trippelsdorf
2015-10-31 20:30 ` Jeff Law
2015-11-02 7:43 ` Thomas Schwinge
2015-11-02 13:51 ` Andrew MacLeod
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=5641113A.6050609@redhat.com \
--to=law@redhat.com \
--cc=amacleod@redhat.com \
--cc=gcc-patches@gcc.gnu.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).