public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: "H.J. Lu" <hjl.tools@gmail.com>
To: Andreas Schwab <schwab@linux-m68k.org>
Cc: Binutils <binutils@sourceware.org>
Subject: Re: PATCH: Add --compress-debug-sections=[none|zlib|zlib-gnu|zlib-gabi] to ld
Date: Tue, 28 Apr 2015 19:29:00 -0000	[thread overview]
Message-ID: <CAMe9rOpoHjGBnGe63VWMsA9zShu7HSFyW0dbVQo6q99wDqC15Q@mail.gmail.com> (raw)
In-Reply-To: <87lhhc2gwk.fsf@igel.home>

On Tue, Apr 28, 2015 at 12:26 PM, Andreas Schwab <schwab@linux-m68k.org> wrote:
> "H.J. Lu" <hjl.tools@gmail.com> writes:
>
>> +set test gabinormal
>> +set test_name "Link with zlib-gabi compressed debug output"
>> +send_log "$READELF -w tmpdir/$test > tmpdir/$test.out\n"
>> +set got [remote_exec host "$READELF -w tmpdir/$test" "" "/dev/null" "tmpdir/$test.out"]
>> +if { [lindex $got 0] != 0 || ![string match "" [lindex $got 1]] } then {
>> +    send_log "$got\n"
>> +    unresolved "$test_name"
>> +}
>> +if { [catch {exec cmp tmpdir/normal.out tmpdir/$test.out}] } then {
>> +    send_log "tmpdir/normal.out tmpdir/$test.out differ.\n"
>> +    fail "$test_name"
>> +} else {
>> +    pass "$test_name"
>> +}
>> +send_log "$READELF -t -W tmpdir/$test > tmpdir/$test.out\n"
>> +set got [remote_exec host "$READELF -t -W tmpdir/$test" "" "/dev/null" "tmpdir/$test.out"]
>> +if { [lindex $got 0] != 0 || ![string match "" [lindex $got 1]] } then {
>> +    send_log "$got\n"
>> +    unresolved "$test_name"
>> +}
>> +if { [regexp_diff tmpdir/$test.out $srcdir/$subdir/$test.rt] } then {
>> +    fail "$test_name"
>> +} else {
>> +    pass "$test_name"
>> +}
>
>   [26] .debug_aranges
>        PROGBITS        0000000000000000 001440 000093 00   0   0 16
>        [0000000000000800]: COMPRESSED
>        ZLIB, 0000000000000180, 16
>
> regexp_diff match failure
> regexp "^ +ZLIB, [0-9a-f]+, 1$"
> line   "       ZLIB, 0000000000000180, 16"
> FAIL: Link with zlib-gabi compressed debug output
>

Which target requires 16-byte alignment on .debug_aranges section?


-- 
H.J.

  reply	other threads:[~2015-04-28 19:29 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-13 12:38 H.J. Lu
2015-04-15  0:55 ` Alan Modra
2015-04-15  2:44   ` H.J. Lu
2015-04-15  3:58     ` Alan Modra
2015-04-15  5:07       ` H.J. Lu
2015-04-28 18:57         ` Andreas Schwab
2015-04-28 19:15           ` H.J. Lu
2015-04-28 19:22             ` Andreas Schwab
2015-04-28 19:25               ` H.J. Lu
2015-04-28 19:46                 ` Andreas Schwab
2015-04-28 19:26         ` Andreas Schwab
2015-04-28 19:29           ` H.J. Lu [this message]
2015-04-28 19:46             ` Andreas Schwab
2015-04-28 20:00               ` H.J. Lu
2015-04-28 20:21                 ` Andreas Schwab
2015-04-28 20:34                   ` H.J. Lu
2015-04-28 20:44                     ` Andreas Schwab
2015-04-28 20:45                       ` H.J. Lu
2015-04-28 20:49                         ` Andreas Schwab
2015-04-28 21:02                           ` H.J. Lu
2015-04-29  7:35             ` Andreas Schwab
2015-04-28 19:36         ` Andreas Schwab
2015-04-28 19:43           ` H.J. Lu

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=CAMe9rOpoHjGBnGe63VWMsA9zShu7HSFyW0dbVQo6q99wDqC15Q@mail.gmail.com \
    --to=hjl.tools@gmail.com \
    --cc=binutils@sourceware.org \
    --cc=schwab@linux-m68k.org \
    /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).