public inbox for java-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jon VanAlten <jon.vanalten@redhat.com>
To: Matthias Klose <doko@ubuntu.com>
Cc: GCJ-patches <java-patches@gcc.gnu.org>,
	Tom Tromey <tromey@redhat.com>,
	       Andrew Haley <aph@redhat.com>
Subject: Re: ping: Re: [patch] update ecj to ecj-3.8.2/4.2.2
Date: Tue, 02 Jul 2013 19:04:00 -0000	[thread overview]
Message-ID: <1437863721.2322487.1372791878657.JavaMail.root@redhat.com> (raw)
In-Reply-To: <51D29F0E.2000400@ubuntu.com>



----- Original Message -----
> From: "Matthias Klose" <doko@ubuntu.com>
> To: "Jon VanAlten" <jon.vanalten@redhat.com>
> Cc: "GCJ-patches" <java-patches@gcc.gnu.org>, "Tom Tromey" <tromey@redhat.com>, "Andrew Haley" <aph@redhat.com>
> Sent: Tuesday, July 2, 2013 3:36:14 AM
> Subject: Re: ping: Re: [patch] update ecj to ecj-3.8.2/4.2.2
> 
> On 06/26/13 21:23, Jon VanAlten wrote:
> > 
> >  checkout:
> > -	cvs -d $(cvsroot) co -r$(TAG) org.eclipse.jdt.core
> > +#	git clone -b R3_8_maintenance
> > git://git.eclipse.org/gitroot/jdt/eclipse.jdt.core.git
> > +#	wget
> > http://git.eclipse.org/c/jdt/eclipse.jdt.core.git/snapshot/$(TAG).tar.gz
> > +	tar xf $(TAG).tar.gz
> > 
> > So "checkout" target no longer does a checkout... seems a bit off. Is
> > the commented git clone line left over from doing some of this before
> > the official tag existed? Might want to drop that, and consider
> > renaming the target to reflect its new behaviour.
> 
> sure, I can rename that.  any suggestion?  The purpose is to make it clear
> where
> the source do come from.

If my reading of this is correct, this make target now does some moving
about of things that are already checked out into the local filesystem.
My suggestion would be to call it "prepare-sources" or just "prepare".

> 
> > +	tar -c -f - -C $(TAG)/org.eclipse.jdt.core/compiler org \
> > +	  | tar -x -f - -C org.eclipse.jdt.core/
> > 
> > Am I missing something or is this equivalent and simpler:
> > 
> > +	mv $(TAG)/org.eclipse.jdt.core/compiler/org org.eclipse.jdt.core/
> > 
> > +	tar -c -f - -C $(TAG)/org.eclipse.jdt.core/batch org \
> > +	  | tar -x -f - -C org.eclipse.jdt.core/
> > 
> > Ditto.
> 
> yes, not having to run the checkout / pull from the web again.
> 

Right, so doing it as "cp -ar" instead of a "mv" would accomplish same?

> > As for the GCCMain portion of the change, yes it looks both necessary
> > and correct. We do same in Fedora package (once again sorry it didn't
> > get posted upstream due to my ignorance), and it would be nice to drop
> > the patch once this is in a release.
> 
> yes, having this upstream would be appreciated.
> 
> So besides the style how to do fetch the sources, this looks ok?
> 

Yep.

> Is there another newer released ecj version which should be used instead?
> 

Let's check the authoritative source[1] for that.  It does seem as though
they've done their 4.3 release, the sources for just ecj can be found
under JDT Core Batch Compiler at [2].  News[3] does mention a few compiler
improvements, but I might suggest to first push update to 3.8 and then
update to latest in separate commit (so anyone else who consumes this can
choose the version they prefer).

cheers,
jon

[1] http://download.eclipse.org/eclipse/downloads/
[2] http://download.eclipse.org/eclipse/downloads/drops4/R-4.3-201306052000/
[3] http://download.eclipse.org/eclipse/downloads/drops4/R-4.3-201306052000/news/eclipse-news-part2.html

  reply	other threads:[~2013-07-02 19:04 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-15 10:21 Matthias Klose
2013-04-15 13:29 ` Andrew Hughes
2013-04-15 13:50   ` Matthias Klose
2013-04-15 14:02     ` Andrew Hughes
2013-04-15 14:08       ` Matthias Klose
2013-04-15 14:22         ` Andrew Hughes
2013-04-15 14:44 ` Jon VanAlten
2013-04-15 21:34   ` Andrew Hughes
2013-04-15 22:39     ` Jon VanAlten
2013-06-20 12:39 ` ping: " Matthias Klose
2013-06-26 19:23   ` Jon VanAlten
2013-07-02  9:36     ` Matthias Klose
2013-07-02 19:04       ` Jon VanAlten [this message]
2013-12-10 15:51         ` Matthias Klose
2013-12-10 16:05           ` Andrew Haley
2013-12-10 16:23             ` Matthias Klose

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=1437863721.2322487.1372791878657.JavaMail.root@redhat.com \
    --to=jon.vanalten@redhat.com \
    --cc=aph@redhat.com \
    --cc=doko@ubuntu.com \
    --cc=java-patches@gcc.gnu.org \
    --cc=tromey@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).