Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Long Li <long21st@yahoo.com>
To: linux-mips@linux-mips.org
Subject: .reginfo and .mdebug section
Date: Tue, 17 Dec 2002 00:43:03 -0800 (PST)	[thread overview]
Message-ID: <20021217084303.20121.qmail@web40407.mail.yahoo.com> (raw)

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.

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?


Thanks a lot!


Long


__________________________________________________
Do you Yahoo!?
Yahoo! Mail Plus - Powerful. Affordable. Sign up now.
http://mailplus.yahoo.com

             reply	other threads:[~2002-12-17  8:43 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-17  8:43 Long Li [this message]
2002-12-17 13:39 ` .reginfo and .mdebug section Ralf Baechle
2002-12-17 18:02 ` H. J. Lu

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=20021217084303.20121.qmail@web40407.mail.yahoo.com \
    --to=long21st@yahoo.com \
    --cc=linux-mips@linux-mips.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