From: "H. J. Lu" <hjl@lucon.org>
To: Long Li <long21st@yahoo.com>
Cc: linux-mips@linux-mips.org
Subject: Re: .reginfo and .mdebug section
Date: Tue, 17 Dec 2002 10:02:03 -0800 [thread overview]
Message-ID: <20021217100203.A8806@lucon.org> (raw)
In-Reply-To: <20021217084303.20121.qmail@web40407.mail.yahoo.com>; from long21st@yahoo.com on Tue, Dec 17, 2002 at 12:43:03AM -0800
On Tue, Dec 17, 2002 at 12:43:03AM -0800, Long Li wrote:
> Hi,
>
> I have some problems after building a linux-mips cross
> compiler on Red Hat7.1.
>
> 1. I tried to compile some c code targetting mips4k,
> which is 32-bit ISA. However, the map file tells me
> that the compiled code are 64-bit, since the address
> are 64-bit.
Mine is 32bit.
>
> 2. When I compiled the c code, I found in the mapfile
> that there are some sections called .reginfo and
> .mdebug. What are those sections? I would like to get
> rid of them. However, they still exists even if I
> deleted the '-g' option for gcc. Is there a way I can
> avoid the .reginfo and .mdebug sections?
Your toolchain is very old. The newer ones no longer use .mdebug.
H.J.
prev parent reply other threads:[~2002-12-17 18:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-17 8:43 .reginfo and .mdebug section Long Li
2002-12-17 13:39 ` Ralf Baechle
2002-12-17 18:02 ` H. J. Lu [this message]
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=20021217100203.A8806@lucon.org \
--to=hjl@lucon.org \
--cc=linux-mips@linux-mips.org \
--cc=long21st@yahoo.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.