public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Thomas Schwinge <thomas@codesourcery.com>
To: Martin Jambor <mjambor@suse.cz>
Cc: Jakub Jelinek <jakub@redhat.com>,
	Cesar Philippidis	<cesar@codesourcery.com>,
	Alexander Monakov <amonakov@ispras.ru>,
	GCC Patches	<gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] omp-low.c split
Date: Tue, 13 Dec 2016 11:39:00 -0000	[thread overview]
Message-ID: <87r35crrca.fsf@hertz.schwinge.homeip.net> (raw)
In-Reply-To: <20161209130821.baeo4o3bd2yazgzz@virgil.suse.cz>

Hi!

On Fri, 9 Dec 2016 14:08:21 +0100, Martin Jambor <mjambor@suse.cz> wrote:
> this is the promised attempt at splitting omp-low.c [...]

Yay!  \o/

I have not yet had a chance to review/test this patch, but I plan to.

A few initial comments from the "bike shed departement"; I understand in
GCC sources it will not be easy to rename stuff (such as files) later, so
we should get the names agreed upon early:

Generally, I agree with your division of "omp-low.c" parts.

>   - move everything that is part of pass_oacc_device_lower,
>     pass_omp_device_lower and pass_omp_target_link to a new file
>     omp-device.h,

Should we call this file "omp-offload.c", as offloading is what this
deals with, is the term we agreed to generally use (as far as I can
tell)?

>   - move all pre-lowering gridification stuff to a new file
>     omp-grid.c.  [...]

Is that code generic enough to not call this file "omp-hsa.c" or similar?

>   - I moved stuff that was used from all over the place to a new file
>     omp-general.c (unless it would mean exposing omp_region or
>     omp_context types).

I'd have called that simply "omp.c".

> I am opened to suggestions what to do differently, names of the file
> are for example of course subject to discussion, and I absolutely
> welcome any review and checking, for one I am not going to pretend I
> understand the stuff I put into omp-device.c.  If however there is
> consensus that we should do something like this, I would like to ask
> the community to freeze omp-low.c file until this gets committed, I
> hope you understand that I am afraid of any conflicts.

I very much understand...  :-| When I had worked on the very same thing
months ago, and my changes went without review/approval for a long time,
I had spent numerous hours on keeping my patch up to date.  So, I'm happy
to see that this is now near approval!  (Even though I don't understand
what's different now from when I worked on the same thing back then...)

I hope to have time later today to review/test your actual patch.


Grüße
 Thomas

  parent reply	other threads:[~2016-12-13 11:39 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-09 13:08 Martin Jambor
2016-12-09 13:25 ` Alexander Monakov
2016-12-09 13:53   ` Martin Jambor
2016-12-09 14:22     ` Jakub Jelinek
2016-12-09 16:19       ` Alexander Monakov
2016-12-13 10:20         ` Martin Jambor
2016-12-13 10:16       ` Martin Jambor
2016-12-13 10:35         ` Jakub Jelinek
2016-12-14 16:56           ` Martin Jambor
2016-12-13 12:58         ` Alexander Monakov
2016-12-13 11:39 ` Thomas Schwinge [this message]
2016-12-13 11:43   ` Jakub Jelinek
2016-12-13 12:42     ` Martin Jambor
2016-12-13 14:48       ` Cesar Philippidis
2016-12-14 13:16       ` Thomas Schwinge
2016-12-14 13:24         ` Martin Jambor
2021-08-04 12:40 ` Thomas Schwinge
2021-08-04 12:45   ` Jakub Jelinek

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=87r35crrca.fsf@hertz.schwinge.homeip.net \
    --to=thomas@codesourcery.com \
    --cc=amonakov@ispras.ru \
    --cc=cesar@codesourcery.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=jakub@redhat.com \
    --cc=mjambor@suse.cz \
    /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).