From: "Hari K. Pyla" <harip@vt.edu>
To: gcc-help@gcc.gnu.org
Cc: Ian Lance Taylor <iant@google.com>
Subject: Re: changes made to gmon-sol2.c not reflected after recompiling gcc
Date: Tue, 28 Nov 2006 22:43:00 -0000 [thread overview]
Message-ID: <456CBCED.8020700@vt.edu> (raw)
In-Reply-To: <m38xhvp7r5.fsf@localhost.localdomain>
Hi Ian,
I am sorry for the typo, you are right I was missing the "not". My host
is i386, Thank you for taking time to reply. I guess I need to get to
glibc sources.
Thanks and Regards,
--Hari
Ian Lance Taylor wrote:
>"Hari K. Pyla" <harip@vt.edu> writes:
>
>
>
>> I edited the following functions in gmon-sol2.c in
>>gcc-4.1.1/gcc/config/i386 directory
>>(i) monstartup()
>>(ii) _mcleanup()
>>(iii) internal_mcount()
>>(iv) moncontrol()
>>basically added some fprintf()'s, changed the filename "gmon.out" to
>>"newgmon.out" in create() and recompiled gcc with the following
>>options
>>./configure
>>make
>>make install
>>
>>The changes do seem to be reflected in the new build of gcc. Is there
>>anything that I am missing. I appreciate you taking time to answer
>>this.
>>
>>
>
>OK, I'm guessing that you're missing a "not" in the first sentence of
>the last paragraph.
>
>The problem is most likely that gmon-sol2.c is not used. You didn't
>mention which type of host you are running on, but gmon-sol2.c is only
>used on x86 Solaris systems.
>
>On other x86 systems, including GNU/Linux, the equivalent code is
>found in the C library. On a GNU/Linux system, you will find the code
>in glibc, in the csu subdirectory.
>
>Ian
>
>
>
prev parent reply other threads:[~2006-11-28 22:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-28 20:13 Hari K. Pyla
2006-11-28 21:43 ` Ian Lance Taylor
2006-11-28 22:43 ` Hari K. Pyla [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=456CBCED.8020700@vt.edu \
--to=harip@vt.edu \
--cc=gcc-help@gcc.gnu.org \
--cc=iant@google.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).