This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Potentially merging the transactional-memory branch into mainline.


Hi,

On Thu, 3 Nov 2011, Aldy Hernandez wrote:

> > re-generates gcc/c-opts.c which was moved to gcc/c-family.  I suppose 
> > sth was screwed up during some trunk->branch merge.  Please review the 
> > patches yourself and look for these issues and fix them.
> 
> Again, can you please hit reload on your browser?
> 
> This was fixed yesterday after the latest merge.

(I downloaded the patch with the superfluous files 64 minutes ago.  Yes, 
now it's partly fixed, but it wasn't yesterday.  Partly because it still 
contains gcc/c-opts.c).

> Or you can just diff the branch yourself and see what's in the branch:
> 
> svn diff --old=svn://gcc.gnu.org/svn/gcc/trunk/@180744
> --new=svn://gcc.gnu.org/svn/gcc/branches/transactional-memory

And how do you propose to meaningfully and easily comment on this diff, 
let those comments be known to you and your answers to that be known to 
me?  eMail seems quite perfect for that.  What's so difficult to just 
split the patches according to some topic or directory 
(frontends/middle-end/back-ends/target-lib/testcase/trans-mem.c) so that 
the pieces aren't larger than say 100k and send them to gcc-patches@?  
Because I do have noticed some (nitpicky if you will) things on the patch, 
and would have simply replied to such mail.


Ciao,
Michael.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]