This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: Split out OMP constructs' SIMD clone supporting code (was: Splitting up gcc/omp-low.c?)
- From: Jakub Jelinek <jakub at redhat dot com>
- To: Thomas Schwinge <thomas at codesourcery dot com>
- Cc: gcc-patches at gcc dot gnu dot org, Bernd Schmidt <bschmidt at redhat dot com>, Martin Jambor <mjambor at suse dot cz>
- Date: Fri, 15 Apr 2016 14:15:42 +0200
- Subject: Re: Split out OMP constructs' SIMD clone supporting code (was: Splitting up gcc/omp-low.c?)
- Authentication-results: sourceware.org; auth=none
- References: <5668638A dot 5030500 at redhat dot com> <20151210080835 dot GX5675 at tucnak dot redhat dot com> <87y48o5toc dot fsf at hertz dot schwinge dot homeip dot net> <87twj54hx6 dot fsf at hertz dot schwinge dot homeip dot net> <87h9f441ti dot fsf at hertz dot schwinge dot homeip dot net> <87ega83phf dot fsf at hertz dot schwinge dot homeip dot net> <20160415111507 dot GL19207 at tucnak dot redhat dot com> <8737qn3x79 dot fsf at hertz dot schwinge dot homeip dot net> <20160415115705 dot GN19207 at tucnak dot redhat dot com> <87y48f2hry dot fsf at hertz dot schwinge dot homeip dot net>
- Reply-to: Jakub Jelinek <jakub at redhat dot com>
On Fri, Apr 15, 2016 at 02:11:45PM +0200, Thomas Schwinge wrote:
> Hi!
>
> On Fri, 15 Apr 2016 13:57:05 +0200, Jakub Jelinek <jakub@redhat.com> wrote:
> > On Fri, Apr 15, 2016 at 01:53:14PM +0200, Thomas Schwinge wrote:
> > > For all the other splitting patches that I have posted/proposed, the idea
> > > then is to commit these onto both gcc-6-branch and trunk?
> >
> > If we branch today, then yes, though the gcc-6-branch commits would need to
> > wait until after 6.1 is released.
>
> Uh. I fear these patches will be a bit of a pain to maintain if there's
> then on-going development in trunk, touching the gcc/omp-low.c file? I
> thought we had agreed to get these cleanup changes into trunk in time for
> the first GCC 6 release, to exactly avoid this kind of pain (that is,
> divergence of the gcc/omp-low.c files in trunk and gcc-6-branch)? :-( I
> have not been aware that you intend to create the gcc-6-branch today, and
> neither have I been aware that once the branch's created, the other
> cleanup changes would have to wait until after the GCC 6.1 release.
> There is no way I can get all this done today, or on the weekend.
Then postpone the rest shortly before 6.1 is released.
We shouldn't have big changes to trunk before 6.1 is released anyway,
otherwise we won't be able to test on the trunk fixes intended also for 6.1.
Jakub