[M3devel] gcc 4.5.0?

[Tony Hosking]

Unfortunately, it has never been as easy as import release, merge to head.  Usually there are many differences that need to be resolved by hand.  But, that is how it should be done.

And in past releases (from v3 to v4) things have changed so drastically in gcc that it has been practically a full report.

As can be seen from the history I previously used the approach you mention last: diff against the reference release and roll the diffs forward into the new version by reapplying the diffs. To be honest I find that better because it forces you to look at every diff in context, so you catch any incompatible changes.

On 20 May 2010, at 07:50, Jay K wrote:

> 
> Tony, what is involved in upgrading to gcc 4.5.0?
> 
> Import unchanged gcc.4-5.0 to the "gcc-releases" branch?
> 
> Merge it to the "gcc" branch?
> 
> And then to head?
> 
> 
> 
> 
> I mean, you know..there are all the directions out there for managing
> external trees, but I think the main missing detail is what
> branches/tag names to use to match previous history, and it isn't
> immediately clear to me..from, um, reading the history (which imho is
> yet another indictment of CVS -- I can't figure out what happened).
> 
> 
> I have gone through the exercise a very small number of times, like once, of importing foreign source into cvs.
> But I haven't ever updated it.
> e.g. cvsup.
> 
> 
> I can also easily enough diff our tree against gcc-4.3.0, overwrite with 4.5.0, and reapply the diffs.
> The diffs are quite small.
> But I know that's not considered the right way.
> 
> 
> (I'm still hoping to switch, like to mercurial or maybe git or maybe monotone..)
> 
> 
>  - Jay
> 
>