From: Ben Elliston <bje@au1.ibm.com>
To: Ashutosh Yeole <ashutoshy@KPITCummins.com>
Cc: binutils@sourceware.org
Subject: Re: NOLOAD problem with binutils 2.16.92
Date: Fri, 28 Jul 2006 07:32:00 -0000 [thread overview]
Message-ID: <20060728073331.GB22431@ozlabs.au.ibm.com> (raw)
In-Reply-To: <4A1BE23A7B777442B60F4B4916AE0F130D0EF070@sohm.kpit.com>
> I had posted a problem related to binutils 2.16.92
>
> Please refer to the following link for the posted problem,
> http://sourceware.org/ml/binutils/2006-07/msg00225.html
> After further investigation, I found that this problem also exists for
> ARM and m32r targets also.
Before we go much further, have you tested with CVS binutils?
Cheers, Ben
next prev parent reply other threads:[~2006-07-28 7:32 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 [this message]
2006-07-31 13:21 ` Ashutosh Yeole
2006-07-31 14:54 ` H. J. Lu
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=20060728073331.GB22431@ozlabs.au.ibm.com \
--to=bje@au1.ibm.com \
--cc=ashutoshy@KPITCummins.com \
--cc=binutils@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).