public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Andrew MacLeod <amacleod@redhat.com>
To: Jeff Law <law@redhat.com>, gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: [patch 1/3] Header file reduction - backend files.
Date: Thu, 22 Oct 2015 22:36:00 -0000	[thread overview]
Message-ID: <56296416.5090402@redhat.com> (raw)
In-Reply-To: <5629623C.8080308@redhat.com>

On 10/22/2015 06:25 PM, Jeff Law wrote:
> On 10/01/2015 08:33 PM, Andrew MacLeod wrote:
>> these are all in the main gcc directory. 297 files total.
>>
>> Everything bootstraps on x86_64-pc-linux-gnu and
>> powerpc64le-unknown-linux-gnu.  All targets in config-list.mk still
>> build. Regressions tests also came up clean.
>>
>> OK for trunk?
> So just to be clear, I'm looking at the backend-reorder patch. Now 
> that I know it's going to be reordering & removing duplicates, I know 
> better what to expect.
>
> Can you please look at data-streamer-{in,out}.c, data-streamer.c, 
> gimplify-me.c.   Maybe its changed recently, but options.h is removed 
> as a duplicate by your patch, but on the trunk, I only see it showing 
> up once (using your tools)
>
show-headers data-streamer.c  -soptions.h
on trunk shows me:
   alias.h
   backend.h
     tm.h
       options.h  (1)               <<-------
         flag-types.h
         i386-opts.h
<...>
   hard-reg-set.h
   options.h  (2)                <<-------
   fold-const.h

so the first occurrence is loaded via tm.h from backend.h


>
>
> I realize it's gotten a little stale, but IMHO once approved, if you 
> need to make adjustments due to changes since you originally produced 
> the patch those adjustments are pre-approved.

yeah. what I've been doing is apply the patch... and anything that fails 
to apply, simply run the tool again on that file...  its easier than 
trying to fix things up :-)

Andrew


  reply	other threads:[~2015-10-22 22:33 UTC|newest]

Thread overview: 65+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-02  2:22 [patch 0/3] Header file reduction Andrew MacLeod
2015-10-02  2:33 ` [patch 3/3] Header file reduction - FE files Andrew MacLeod
2015-10-02  2:33 ` [patch 2/3] Header file reduction - config files Andrew MacLeod
2015-10-02  2:33 ` [patch 1/3] Header file reduction - backend files Andrew MacLeod
2015-10-07 22:02   ` Jeff Law
2015-10-07 23:09     ` Andrew MacLeod
2015-10-08 13:37     ` [patch] header file re-ordering Andrew MacLeod
2015-10-08 15:29       ` Jeff Law
2015-10-11 20:58       ` [BUILDROBOT] Bootstrap broken in Ada (was: [patch] header file re-ordering.) Jan-Benedict Glaw
2015-10-11 22:27         ` [BUILDROBOT] Bootstrap broken in Ada Jeff Law
2015-10-11 22:35           ` Jan Hubicka
2015-10-12  8:04       ` [patch] header file re-ordering Jeff Law
2015-10-14 14:05         ` Andrew MacLeod
2015-10-19 21:05           ` Jeff Law
2015-10-16 19:52         ` config header file reduction patch checked in Andrew MacLeod
2015-10-16 20:17           ` Andrew MacLeod
2015-10-18  9:34           ` Iain Sandoe
2015-10-19 15:55             ` Andrew MacLeod
2015-10-23 17:02               ` Bernd Schmidt
2015-10-23 17:22                 ` Mike Stump
2015-10-23 17:26                   ` Bernd Schmidt
2015-10-23 17:36                     ` Andrew MacLeod
2015-10-23 17:49                       ` Mike Stump
2015-10-23 17:39                     ` Mike Stump
2015-10-22 21:07       ` [patch] header file re-ordering Jeff Law
2015-10-22 21:21         ` Andrew MacLeod
2015-10-22 22:25           ` Jeff Law
2015-10-23 19:14       ` Jeff Law
2015-10-23 19:28         ` Andrew MacLeod
2015-10-22 22:33   ` [patch 1/3] Header file reduction - backend files Jeff Law
2015-10-22 22:36     ` Andrew MacLeod [this message]
2015-10-23  6:22     ` Jeff Law
2015-10-23 12:26       ` Andrew MacLeod
2015-10-23 15:15         ` Jeff Law
2015-10-23 16:30           ` Andrew MacLeod
2015-10-05 13:55 ` [patch 0/3] Header file reduction Bernd Schmidt
2015-10-05 14:10   ` Richard Biener
2015-10-05 20:10   ` Andrew MacLeod
2015-10-05 20:37     ` Bernd Schmidt
2015-10-05 21:11       ` Andrew MacLeod
2015-10-06  3:03         ` [patch 0/3] Header file reduction. - unified patches Andrew MacLeod
2015-10-06 21:55         ` [patch 0/3] Header file reduction Jeff Law
2015-10-06 21:44     ` Jeff Law
2015-10-07  8:16       ` Richard Biener
2015-10-08 15:48         ` Michael Matz
2015-10-05 21:18   ` [patch 4/3] Header file reduction - Tools for contrib Andrew MacLeod
2015-10-06 10:27     ` Bernd Schmidt
2015-10-06 12:02       ` Bernd Schmidt
2015-10-06 14:04         ` Andrew MacLeod
2015-10-06 14:57           ` Bernd Schmidt
2015-10-06 19:19             ` Andrew MacLeod
2015-10-06 20:37               ` Bernd Schmidt
2015-10-06 21:30                 ` Jeff Law
2015-10-06 22:43                 ` Andrew MacLeod
2015-10-06 21:27           ` Jeff Law
2015-10-06 16:32         ` Joseph Myers
2015-10-06 19:18         ` Andrew MacLeod
2015-10-07 16:35         ` Andrew MacLeod
2015-10-14 15:14           ` [patch 4/3] Header file reduction - Tools for contrib - second cut Andrew MacLeod
2015-11-03  6:06             ` Jeff Law
2015-11-03 13:24               ` Andrew MacLeod
2015-11-03 14:00                 ` Jeff Law
2015-11-03 14:19                   ` Andrew MacLeod
2015-11-10 21:16                     ` Jeff Law
2015-10-08 16:31         ` [patch 4/3] Header file reduction - Tools for contrib David Malcolm

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=56296416.5090402@redhat.com \
    --to=amacleod@redhat.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=law@redhat.com \
    /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).