All of lore.kernel.org
 help / color / mirror / Atom feed
* .reginfo and .mdebug section
@ 2002-12-17  8:43 Long Li
  2002-12-17 13:39 ` Ralf Baechle
  2002-12-17 18:02 ` H. J. Lu
  0 siblings, 2 replies; 3+ messages in thread
From: Long Li @ 2002-12-17  8:43 UTC (permalink / raw)
  To: linux-mips

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

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: .reginfo and .mdebug section
  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
  1 sibling, 0 replies; 3+ messages in thread
From: Ralf Baechle @ 2002-12-17 13:39 UTC (permalink / raw)
  To: Long Li; +Cc: linux-mips

On Tue, Dec 17, 2002 at 12:43:03AM -0800, Long Li wrote:

> 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?

.reginfo is MIPS ABI mandated brain damage described the register usage of
a given object or shared object.  I know of nothing that actually is using
these sections.  It's always just 24 bytes so not really worth alot of fuzz
though.  With some binutils versions you can remove this section with
objcopy --remove-section=.reginfo.  Some binutils version however will just
create a new .reginfo section during objcopy so with those this won't work.

.mdebug is the MIPS ABI mdebug stuff, debug information.  You should be
able to get rid of those with -g, at least my tools here don't create it
by default.

  Ralf

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: .reginfo and .mdebug section
  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
  1 sibling, 0 replies; 3+ messages in thread
From: H. J. Lu @ 2002-12-17 18:02 UTC (permalink / raw)
  To: Long Li; +Cc: linux-mips

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.

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2002-12-17 18:02 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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 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.