public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Tristan Gingold <gingold@adacore.com>
To: Roland McGrath <mcgrathr@google.com>
Cc: "binutils@sourceware.org" <binutils@sourceware.org>
Subject: Re: PR ld/16643: ARM: BFD_ASSERT when only ref to a GC'd symbol is in a stripped section
Date: Thu, 06 Mar 2014 08:18:00 -0000	[thread overview]
Message-ID: <6445F8EC-8A18-474F-B854-5827A08925DE@adacore.com> (raw)
In-Reply-To: <CAB=4xhoYWjL-Ss2Mqw4PFWK+FdGv5XPD=EyAcXMB-xg40ZURVA@mail.gmail.com>


On 05 Mar 2014, at 19:07, Roland McGrath <mcgrathr@google.com> wrote:

> ping.
> Still looking for maintainer approval to commit my test case.
> Still looking for release maintainer approval to backport fix+test to 2.24.

OK for 2.24 once approved on trunk.

Tristan.

> 
> On Fri, Feb 28, 2014 at 9:44 AM, Roland McGrath <mcgrathr@google.com> wrote:
>> On Thu, Feb 27, 2014 at 4:25 PM, Alan Modra <amodra@gmail.com> wrote:
>>> Here you go, this cures your testcase.
>> 
>> Great!  Thanks a lot.
>> 
>> OK to commit the test case now?
>> 
>> OK to backport both fix and test to 2.24?
>> 
>> 
>> Thanks,
>> Roland
>> 
>> 
>> ld/testsuite/
>> 2014-02-28  Roland McGrath  <mcgrathr@google.com>
>> 
>>        PR ld/16643
>>        * ld-arm/gc-hidden-strip.d: New file.
>>        * ld-arm/gc-hidden-strip-unused.s: New file.
>>        * ld-arm/gc-hidden-strip-main.s: New file.
>>        * ld-arm/arm-elf.exp: Run the new test.
>> 
>> --- a/ld/testsuite/ld-arm/arm-elf.exp
>> +++ b/ld/testsuite/ld-arm/arm-elf.exp
>> @@ -842,3 +842,4 @@ if { ![istarget "arm*-*-nacl*"] } {
>> }
>> run_dump_test "unresolved-2"
>> run_dump_test "gc-hidden-1"
>> +run_dump_test "gc-hidden-strip"
>> --- /dev/null
>> +++ b/ld/testsuite/ld-arm/gc-hidden-strip-main.s
>> @@ -0,0 +1,6 @@
>> +       .text
>> +       .globl foo
>> +       .type foo, %function
>> +foo:
>> +       bx lr
>> +       .size foo, . - foo
>> --- /dev/null
>> +++ b/ld/testsuite/ld-arm/gc-hidden-strip-unused.s
>> @@ -0,0 +1,11 @@
>> +       .section .data.unused_item,"aw",%progbits
>> +       .p2align 2
>> +       .global unused_item
>> +       .hidden unused_item
>> +       .type unused_item, %object
>> +       .size unused_item, 4
>> +unused_item:
>> +       .word 1
>> +
>> +       .section .debug_blah,"",%progbits
>> +       .word unused_item
>> --- /dev/null
>> +++ b/ld/testsuite/ld-arm/gc-hidden-strip.d
>> @@ -0,0 +1,15 @@
>> +#source: gc-hidden-strip-main.s
>> +#source: gc-hidden-strip-unused.s
>> +#ld: --gc-sections --shared --strip-all
>> +#objdump: -RT
>> +# This test is only valid on ELF based ports.
>> +# not-target: *-*-*coff *-*-pe *-*-wince *-*-*aout* *-*-netbsd *-*-riscix*
>> +
>> +# See PR ld/16643: the only reference to a GC'd symbol is in a stripped
>> +# section, trigging a BFD_ASSERT.
>> +
>> +.*:     file format elf32-.*
>> +
>> +DYNAMIC SYMBOL TABLE:
>> +0+[0-9a-f]+ l\s+d\s+\.text\s+0+\s+\.text
>> +#pass

  reply	other threads:[~2014-03-06  8:18 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-27 23:07 Roland McGrath
2014-02-28  0:25 ` Alan Modra
2014-02-28 17:44   ` Roland McGrath
2014-03-05 18:07     ` Roland McGrath
2014-03-06  8:18       ` Tristan Gingold [this message]
2014-03-06 17:54         ` Roland McGrath
2014-03-06  8:55       ` Nicholas Clifton
2014-03-06 17:50         ` Roland McGrath

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=6445F8EC-8A18-474F-B854-5827A08925DE@adacore.com \
    --to=gingold@adacore.com \
    --cc=binutils@sourceware.org \
    --cc=mcgrathr@google.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).