public inbox for prelink@sourceware.org
 help / color / mirror / Atom feed
From: Filippo ARCIDIACONO <filippo.arcidiacono@st.com>
To: <prelink@sourceware.org>
Subject: RE: [PATCH] Add TLS support for SH architecture.
Date: Wed, 08 Jul 2009 15:58:00 -0000	[thread overview]
Message-ID: <010601c9ffe4$e087c3b0$1a8b340a@st.com> (raw)
In-Reply-To: <004901c9fa5d$f2cf1550$1a8b340a@st.com>

 

[SNIP]

> I looked again at the test failure, indeed it seems the 
> problem is in our libstdc++, While all other DSOs have a 
> valid dwarf2 .debug_aranges.
> Our libstdc++ .debug_aranges seems to be not valid.
> 
> readelf --debug-dump=aranges ./libstdc++.so.6
> 
> The section .debug_aranges contains:
> 
>   Length:                   1028 
>   Version:                  2    
>   Offset into .debug_info:  0x0  
>   Pointer Size:             4    
>   Segment Size:             0    
> 
>     Address    Length
> 00000000 00000000    <----- Spurious 8 bytes I skipped
> 319c7b00 00000020
> 319c7b20 00000020
> 319c7b40 00000054
> 319c7b94 00000040
> 319c7bd4 00000012
> :
> :
> 
> I'll have a look at binutils. So I agree with you to discard 
> this part of the patch.

This isn't sh4 specific issue but it is a known gcc bug in 4.2.4 version, 
fixed in 4.3.
See http://gcc.gnu.org/ml/gcc-patches/2007-08/msg01200.html for detail, 
Where there is also a reference to prelink sanity check.

> 
[SINP]

Filippo.

  reply	other threads:[~2009-07-08 15:58 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-01 15:09 Filippo ARCIDIACONO
2009-07-08 15:58 ` Filippo ARCIDIACONO [this message]
  -- strict thread matches above, loose matches on Subject: below --
2009-07-01  7:04 Filippo ARCIDIACONO
2009-07-01  8:55 ` Jakub Jelinek

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='010601c9ffe4$e087c3b0$1a8b340a@st.com' \
    --to=filippo.arcidiacono@st.com \
    --cc=prelink@sourceware.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).