2.22.1 Possible -> Yes!

Tristan Gingold gingold@adacore.com
Fri Apr 27 12:16:00 GMT 2012


On Apr 26, 2012, at 7:30 PM, Doug Kwan (關振德) wrote:

> There are both binutils-2_22_branch and binutils-2_22-branch.  Which
> branch should I check in my patches?

In binutils-2_22-branch

I haven't yet investigated where the _branch comes from.

Tristan.

> 
> -Doug
> 
> $ cvs status -v ChangeLog | grep branch:
> 	binutils-2_22_branch     	(branch: 1.1006.4)
> 	gdb_7_4-branch           	(branch: 1.1012.2)
> 	binutils-2_22-branch     	(branch: 1.1006.2)
> 	gdb_7_3-branch           	(branch: 1.983.2)
> 	binutils-2_21-branch     	(branch: 1.938.2)
>       ....
> 
> 
> 
> 
> On Thu, Apr 26, 2012 at 9:41 PM, Doug Kwan (關振德) <dougkwan@google.com> wrote:
>> I have some ARM gold patches I will commit them today.
>> 
>> On Thu, Apr 26, 2012 at 9:29 PM, Tristan Gingold <gingold@adacore.com> wrote:
>>> 
>>> On Apr 26, 2012, at 3:28 AM, Mike Frysinger wrote:
>>> 
>>>> On Wednesday 25 April 2012 09:18:15 Joel Sherrill wrote:
>>>>> Tristan you mentioned that you are not sure there will
>>>>> be a 2.22.1.  Does that mean 2.23 is close or that
>>>>> you don't see enough issues to justify 2.22.1?
>>>> 
>>>> fwiw, ppc32 is pretty badly hosed in the 2.22 release.  just about every ELF
>>>> produced includes TEXTRELs.  the fix for it is already in the 2.22 branch.
>>>> 
>>>> hppa32 has incorrect TLS relocation behavior, and plt/ifunc behavior -- also
>>>> kind of bad.  the fixes are already in the 2.22 branch.
>>>> 
>>>> s390x fails to build, but that isn't technically a regression from 2.21, so
>>>> maybe not a big deal.
>>>> 
>>>> so might be nice to have a 2.22.1 release i think :).
>>> 
>>> Ok, I will make a 2.22.1 release.
>>> 
>>> If anyone has patches to backport, please speak up.
>>> 
>>> Tristan.
>>> 



More information about the Binutils mailing list