From: Brady Brown <bbrown@ti.com>
To: SGI news group <linux-mips@oss.sgi.com>
Subject: Sign extended 64bit address
Date: Tue, 20 Mar 2001 17:04:07 -0700 [thread overview]
Message-ID: <3AB7EFF7.A20E4FF3@ti.com> (raw)
I have run into the earlier mentioned problem of objcopy not correctly
dealing with the sign extended 64 bit address generated by the new
tools. Is there an update on this issue? Any good work-arounds or short
time solutions?
--
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Brady Brown (bbrown@ti.com) Work:(801)619-6103
Texas Instruments: Broadband Access Group
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
next reply other threads:[~2001-03-20 23:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-21 0:04 Brady Brown [this message]
2001-03-21 4:04 ` Sign extended 64bit address Ralf Baechle
2001-03-21 16:58 ` Brady Brown
2001-03-21 17:10 ` Ralf Baechle
2001-03-21 19:15 ` Brady Brown
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=3AB7EFF7.A20E4FF3@ti.com \
--to=bbrown@ti.com \
--cc=linux-mips@oss.sgi.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