From: "H. J. Lu" <hjl@lucon.org>
To: Ashutosh Yeole <ashutoshy@KPITCummins.com>
Cc: binutils@sourceware.org, Ben Elliston <bje@au1.ibm.com>
Subject: Re: NOLOAD problem with binutils 2.16.92
Date: Mon, 31 Jul 2006 14:54:00 -0000 [thread overview]
Message-ID: <20060731145442.GA30747@lucon.org> (raw)
In-Reply-To: <4A1BE23A7B777442B60F4B4916AE0F130D2059AB@sohm.kpit.com>
On Mon, Jul 31, 2006 at 06:51:17PM +0530, Ashutosh Yeole wrote:
> Hi,
> I have tried this problem using the latest snapshot of binutils dated
> 30th July 2006, however the same problem still exists. With this
> snapshot, I tested for SH as well as H8 targets.
>
> http://lists.gnu.org/archive/html/bug-binutils/2006-07/msg00041.html
> (Link to the actual problem)
Please open a bug report at:
http://www.sourceware.org/bugzilla/
> /* If the section type is unspecified, we set it based on
> asect->flags. */
> - if (this_hdr->sh_type == SHT_NULL)
> + if ((this_hdr->sh_type == SHT_NULL) || (this_hdr->sh_type ==
> SHT_PROGBITS))
> {
> if ((asect->flags & SEC_GROUP) != 0)
> this_hdr->sh_type = SHT_GROUP;
It doesn't look right.
>
> However I am not very sure about the patch and I understand it may be
> fixed somewhere else. I would like to know your comments on the same.
>
You need to find where and why this_hdr->sh_type is set to
SHT_PROGBITS in the first place.
H.J.
next prev parent reply other threads:[~2006-07-31 14:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-26 10:01 Ashutosh Yeole
2006-07-26 20:11 ` Ramana Radhakrishnan
2006-07-28 7:32 ` Ben Elliston
2006-07-31 13:21 ` Ashutosh Yeole
2006-07-31 14:54 ` H. J. Lu [this message]
2006-07-31 20:03 ` H. J. Lu
2006-07-31 23:45 ` Alan Modra
2006-08-01 17:43 ` H. J. Lu
-- strict thread matches above, loose matches on Subject: below --
2006-07-18 12:54 Ashutosh Yeole
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=20060731145442.GA30747@lucon.org \
--to=hjl@lucon.org \
--cc=ashutoshy@KPITCummins.com \
--cc=binutils@sourceware.org \
--cc=bje@au1.ibm.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).