This is the mail archive of the mailing list for the binutils 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: Release 2.23 ?

On Oct 22, 2012, at 6:04 PM, Fred Cooke wrote:

> So is that to say that all test suite changes applied to trunk since
> forking are also included in the branch and that none fail?

No and no.  Test suite changes that were part of patches applied to the
branch are included in the branch.  And some may fail on some targets.

Here is the list of targets without failures:

aarch64-linux: OK
alpha-linux: OK
arm-eabi: OK
avr: OK
cr16-elf: OK
crx-elf: OK
d10v-elf: OK
frv-elf: OK
hppa-linux-gnu: OK
ia64-linux: OK
m32c-elf: OK
m32r-elf: OK
m68k-elf: OK
mcore-elf: OK
mips-elf: OK
mips-linux: OK
mips64-elf: OK
mn10300-elf: OK
msp430-elf: OK
powerpc-elf: OK
powerpc64-elf: OK
s390-linux: OK
sh4-elf: OK
sh64-elf: OK
sparc-elf: OK
sparc64-elf: OK
spu-elf: OK
v850-elf: OK
vax-netbsdelf: OK
x86_64-pc-linux-gnu: OK
xstormy16-elf: OK
xtensa-elf: OK

> Does this
> imply that the fixes themselves were also included? Or that other
> patches introduced broke things on trunk and then re-fixed them?

We simply backported some important patches from trunk to the branch.


> On Mon, Oct 22, 2012 at 4:21 PM, Tristan Gingold <> wrote:
>> On Oct 22, 2012, at 12:12 PM, Fred Cooke wrote:
>>> There seem to have been a lot of stability changes and bug fixes going
>>> into trunk in the last little while since it got forked. Would it be
>>> beneficial to apply the test suite changes from trunk to the release
>>> branch so as to ascertain whether some or all of those fixes are
>>> needed for the release branch too?
>> That's what we do, generally.  If the patch set contains testsuite changes,
>> they are applied on the branch too.
>> Tristan.

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