Re: [Gcc4cli-devel] README

[Erven R. <erv...@in...>]

I think it is not too bad: July 2009.

Since then, we could add:


2010-03
	Move binutils to a new repository.
	Cleanup of binutils: improved code size thanks to the use of the short forms of 
ldc/ldloc/stloc/ldarg and branch opcodes.
	Several bug fixes.
2010-01
	Emission source location when -g is active.



Anything else?

--
Erven.

Andrea Carlo Ornstein a écrit :
> http://gcc.gnu.org/projects/cli.html
> It is probably a little out of date :)
> 
> On Tue, Mar 23, 2010 at 2:50 PM, Erven Rohou <erv...@in...> wrote:
>> Andrea Carlo Ornstein a écrit :
>>> I already changed the wiki on sourceforge
>>> https://sourceforge.net/apps/mediawiki/gcc4cli/index.php?title=Main_Page
>>> I cannot change the README and the html pages on gcc from here.
>> I just updated the README.
>> What HTML page are you talking about?
>>
>>> I am ok with the changes and also having the mono based one as preferred.
>>>
>>> After a short period of transition I would like to empty the dirs
>>> svn://gcc.gnu.org/svn/gcc/branches/st/binutils and
>>> svn://gcc.gnu.org/svn/gcc/branches/st/mono-based-binutils and keep
>>> there (in both) just a README file saying that the code has been moved
>>> to the sourceforge project with the proper links
>> Fine with me.
>>
>>> Erven, you know better than me who are the users at this point,
>>> I let you decide how long is this 'short period' :)
>> I think we mostly have IBM Haifa, INRIA, and Politecnico di Milano (ie
>> Harvard).
>> I am going to tell them.
>>
>> --
>> Erven.
>>
>>> I will create a couple of mailing list also for cli binutils (one for
>>> the ci and one for the development discussions)
>>>
>>> Andrea
>>>
>>> On Tue, Mar 23, 2010 at 8:40 AM, Erven Rohou <erv...@in...> wrote:
>>>> Ciao Andrea,
>>>>
>>>> Many thanks for the various fixes.
>>>> Probably, we should update the README in gcc.../branches/st/README to
>>>> reflect
>>>> the new binutils location.
>>>>
>>>> I am also tempted to change the order of the sections: first the build
>>>> instructions for the Mono toolchain, then DotGnu. Maybe we can also say
>>>> the Mono
>>>> is the preferred way?
>>>>
>>>> --
>>>> Erven.
>