public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Jan Hubička" <honza.hubicka@gmail.com>
To: "Martin Liška" <mliska@suse.cz>
Cc: Uros Bizjak <ubizjak@gmail.com>, Jeff Law <law@redhat.com>,
		Eric Gallager <egall@gwmail.gwu.edu>,
	GCC Development <gcc@gcc.gnu.org>,
	"H.J. Lu" <hjl.tools@gmail.com>,
		Jakub Jelinek <jakub@redhat.com>
Subject: Re: [WIP][RFC] split of i386.c
Date: Thu, 18 Apr 2019 11:56:00 -0000	[thread overview]
Message-ID: <CAJf+ejdKUZt2SEr5b22YMcP2KVjmK+YDkdeicTbc1WkWo2DVyw@mail.gmail.com> (raw)
In-Reply-To: <b1969af9-cd48-e154-9f2e-55f124032547@suse.cz>

Hello,
the patch looks good to me. I think in the copyright comment you want to
copy all the years of copyright of original i386.c since the code is not
from 2019. also there are missing licence comments in the .h files.
I would probably put the bigger machine specific optimization passes into
separate files (these have noreason to be globbed).
It will also make it more obvoius that i386 has couple of optimization
passes. Why scalar chain needs to be exported?

I think it would be nice to commit the patch early stage1 :)
Honza



On Mon, Mar 18, 2019 at 3:19 PM Martin Liška <mliska@suse.cz> wrote:

> Hi.
>
> I'm sending first version of the split, which has following
> statistics:
>
>  gcc/config.gcc                  |     5 +-
>  gcc/config/i386/i386-builtins.c |  2563 ++++++++++
>  gcc/config/i386/i386-builtins.h |   314 ++
>  gcc/config/i386/i386-expand.c   | 19868
> +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>  gcc/config/i386/i386-expand.h   |    40 +
>  gcc/config/i386/i386-features.c |  2854 +++++++++++
>  gcc/config/i386/i386-features.h |   179 +
>  gcc/config/i386/i386-options.c  |  3678 ++++++++++++++
>  gcc/config/i386/i386-options.h  |    76 +
>  gcc/config/i386/i386-protos.h   |     4 -
>  gcc/config/i386/i386.c          | 62939
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>  gcc/config/i386/i386.h          |     9 +
>  gcc/config/i386/t-i386          |    16 +
>  13 files changed, 46542 insertions(+), 46003 deletions(-)
>
> The newly created files have following content:
> - i386-builtins.c - builtin-in handling, __builtin_cpu_is and
> __builtin_cpu_supports, target pragma handling
> - i386-expand.c - all scalar and vector expansion code
> - i386-features.c - contains isolated target features - vzerotoupper, stv,
> cet, rpad, multi-versioning,
> - i386-options.c - option related functions, target attribute handling
>
> Now the i386.c file is down in size:
> 23038 gcc/config/i386/i386.c
>
> Question is whether I should continue or not? Remaining content of the
> file is made of
> various costing functions, print_reg*, various target hooks, coff, ms_abi,
> retpolines,
> output-functions, etc. I don't see any further split point which should
> define a new
> file.
>
> Patch:
> https://drive.google.com/file/d/1SiNcR35DHMNBumyg5ltbOozEJ5Q0ajKn/view?usp=sharing
>
> Thoughts?
> Thanks,
> Martin
>

  reply	other threads:[~2019-04-18 11:56 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-12 15:08 [RFC] " Martin Liška
2019-03-12 20:50 ` Eric Gallager
2019-03-12 20:54   ` Jeff Law
2019-03-13 13:56     ` Uros Bizjak
     [not found]       ` <e1ec1b7b-851d-846e-c544-1f92fef0bd04@suse.cz>
2019-03-18 14:19         ` [WIP][RFC] " Martin Liška
2019-04-18 11:56           ` Jan Hubička [this message]
2019-04-23 10:12             ` Martin Liška
2019-03-13 12:55 ` [RFC] " 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=CAJf+ejdKUZt2SEr5b22YMcP2KVjmK+YDkdeicTbc1WkWo2DVyw@mail.gmail.com \
    --to=honza.hubicka@gmail.com \
    --cc=egall@gwmail.gwu.edu \
    --cc=gcc@gcc.gnu.org \
    --cc=hjl.tools@gmail.com \
    --cc=jakub@redhat.com \
    --cc=law@redhat.com \
    --cc=mliska@suse.cz \
    --cc=ubizjak@gmail.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).