This is the mail archive of the gcc-bugs@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]

Re: -pg vs regparm(2) on linux

To: Doug Evans <dje at transmeta dot com>
Subject: Re: -pg vs regparm(2) on linux
From: Richard Henderson <rth at redhat dot com>
Date: Sun, 25 Mar 2001 01:50:39 -0800
Cc: gcc-bugs at gcc dot gnu dot org
References: <200103242250.OAA30420@casey.transmeta.com> <20010325013011.A7898@redhat.com> <15037.48587.191598.117121@casey.transmeta.com>

On Sun, Mar 25, 2001 at 01:43:39AM -0800, Doug Evans wrote:
> If I wanted to, I'm guessing all I need to do is
> hack FUNCTION_PROFILER and maybe write my own mcount.
> Right?

Actually, there is some flag that says not to pass that
silly data segment variable that mcount doesn't use, 
which will avoid clobbering edx or whatever it is.

> Where are the sources for linux mcount?

glibc/sysdeps/i386/i386-mcount.S, which apparently already
does save all the required registers.

r~

Follow-Ups:
- Re: -pg vs regparm(2) on linux
  - From: Doug Evans
- Re: -pg vs regparm(2) on linux
  - From: Zack Weinberg

References:
- -pg vs regparm(2) on linux
  - From: Doug Evans
- Re: -pg vs regparm(2) on linux
  - From: Richard Henderson
- Re: -pg vs regparm(2) on linux
  - From: Doug Evans

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]