public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Tristan Gingold <gingold@adacore.com>
To: Matthew Gretton-Dann <matthew.gretton-dann@arm.com>
Cc: binutils Development <binutils@sourceware.org>
Subject: Re: Release 2.22: Next week ...
Date: Thu, 17 Nov 2011 15:20:00 -0000	[thread overview]
Message-ID: <1B6432BB-4317-4E85-8CE8-C7991F4615CA@adacore.com> (raw)
In-Reply-To: <4EC523DF.5060403@arm.com>


On Nov 17, 2011, at 4:10 PM, Matthew Gretton-Dann wrote:

> On 17/11/11 14:50, Tristan Gingold wrote:
>> On Nov 9, 2011, at 10:25 AM, Tristan Gingold wrote:
>> 
>>> Hi,
>>> 
>>> I plan to make the 2.22 release next week.
>>> There are still a few pending back ports: micromips and 'V2 of get symbol linker plugin interface' come to my mind.
>>> 
>>> As usual, speak up if you think I missed something.
>> 
>> I have run the testsuite for most of the targets.  I think there aren't blocking regressions for a 22.0, although I think it would be nice to clean-up arm-eabi and mips*-* for the 22.1
> 
>> arm-eabi: FAIL: R_ARM_THM_JUMP24 Relocation veneers: Long
>> arm-eabi: FAIL: R_ARM_THM_JUMP24 Relocation veneers: Short 1
>> arm-eabi: FAIL: R_ARM_THM_JUMP24 Relocation veneers: Short 2
> 
> I thought I had fixed these with:
> 	http://sourceware.org/ml/binutils/2011-11/msg00072.html
> 
> Which was committed:
> 	http://sourceware.org/ml/binutils-cvs/2011-11/msg00042.html
> 
> When I run the tests myself targetting arm-none-eabi they pass, as they also (I am assuming) in your arm-linux-gnueabi run (you didn't highlight them there).

Yes, I was surprised too.

> Do you mind sending me the appropriate part of ld.log from the testrun and I will try to see if I can reproduce the failure?

Sure:

/tmp/binutils-2.21.90-sc/objs-arm-eabi/ld/../gas/as-new    -o tmpdir/jump-reloc-veneers.o -march=armv7-a -mthumb /tmp/binutils-2.21.90-sc/binutils-2.21.90/ld/testsuite/ld-arm/jump-reloc-veneers.s
Executing on host: sh -c {/tmp/binutils-2.21.90-sc/objs-arm-eabi/ld/../gas/as-new    -o tmpdir/jump-reloc-veneers.o -march=armv7-a -mthumb /tmp/binutils-2.21.90-sc/binutils-2.21.90/ld/testsuite/ld-arm/jump-reloc-veneers.s 2>&1}  /dev/null ld.tmp (timeout = 300)
/tmp/binutils-2.21.90-sc/objs-arm-eabi/ld/ld-new   -o tmpdir/jump-reloc-veneers-short1 -L/tmp/binutils-2.21.90-sc/binutils-2.21.90/ld/testsuite/ld-arm --no-fix-arm1176 --section-start destsect=0x00009000 --section-start .text=0x8000 tmpdir/jump-reloc-veneers.o
Executing on host: sh -c {/tmp/binutils-2.21.90-sc/objs-arm-eabi/ld/ld-new   -o tmpdir/jump-reloc-veneers-short1 -L/tmp/binutils-2.21.90-sc/binutils-2.21.90/ld/testsuite/ld-arm --no-fix-arm1176 --section-start destsect=0x00009000 --section-start .text=0x8000 tmpdir/jump-reloc-veneers.o 2>&1}  /dev/null ld.tmp (timeout = 300)
Executing on host: sh -c {/tmp/binutils-2.21.90-sc/objs-arm-eabi/ld/../binutils/objdump -d tmpdir/jump-reloc-veneers-short1 >dump.out 2>ld.stderr}  /dev/null  (timeout = 300)
/tmp/binutils-2.21.90-sc/objs-arm-eabi/ld/../binutils/objdump -d tmpdir/jump-reloc-veneers-short1
regexp_diff match failure
regexp "^    9000:      e7fe            b.n     9000 <dest>$"
line   "    9000:       f7ff bffe       b.w     9000 <dest>"
FAIL: R_ARM_THM_JUMP24 Relocation veneers: Short 1

Tell me if you need more.

Tristan.

  reply	other threads:[~2011-11-17 15:20 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-22  9:17 Release 2.22: branch created Tristan Gingold
2011-09-23 15:57 ` H.J. Lu
2011-09-24 19:53 ` Andreas Schwab
2011-09-25 18:07 ` Dave Korn
2011-09-26  9:43   ` Tristan Gingold
2011-10-09 13:17     ` Christopher Faylor
2011-10-11  2:41       ` Dave Korn
2011-10-16 14:49 ` Eric Botcazou
2011-10-17  0:57   ` David Miller
2011-10-17  1:51   ` David Miller
2011-10-17  9:33     ` Release 2.22: branch create Eric Botcazou
2011-10-17 20:45       ` David Miller
2011-10-18 20:47       ` David Miller
2011-10-18 22:21         ` Ian Lance Taylor
2011-10-18 22:52         ` Eric Botcazou
2011-10-18 23:22           ` David Miller
2011-10-17  7:22   ` Release 2.22: branch created Tristan Gingold
2011-11-09  9:26 ` Release 2.22: Next week Tristan Gingold
2011-11-17 14:51   ` Tristan Gingold
2011-11-17 15:10     ` Matthew Gretton-Dann
2011-11-17 15:20       ` Tristan Gingold [this message]
2011-11-17 17:34         ` Matthew Gretton-Dann
2011-11-18 11:03           ` Tristan Gingold
2011-11-18  7:48         ` Doug Kwan (關振德)
2011-11-21  9:43           ` Tristan Gingold
2011-12-18 17:45 ` James Murray
2011-12-19  9:35   ` Tristan Gingold
2011-12-19 19:45     ` James Murray
2011-12-20 13:51       ` Release 2.22: Next week ... (m68hc11 testsuite) James Murray
2011-12-20 13:56         ` Tristan Gingold
2011-12-20 14:49           ` James Murray
2011-12-29 15:46             ` James Murray
2011-12-30  2:13               ` James Murray
2012-01-02 23:04                 ` James Murray
2012-02-09 12:53                 ` m68hc11 trampolines Alan Modra
2012-02-13  2:32                   ` Alan Modra
2012-02-14 23:08                     ` James Murray
2012-02-14 23:50                       ` Alan Modra
2012-02-14 23:51                       ` Jeffrey Walton
2012-02-15 19:38                         ` James Murray

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1B6432BB-4317-4E85-8CE8-C7991F4615CA@adacore.com \
    --to=gingold@adacore.com \
    --cc=binutils@sourceware.org \
    --cc=matthew.gretton-dann@arm.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).