From: <perugupa@csee.wvu.edu>
To: <wilson@specifixinc.com>
Cc: <gcc@gcc.gnu.org>
Subject: Re: HELP: GCC Passes and Files
Date: Mon, 07 Jun 2004 15:11:00 -0000 [thread overview]
Message-ID: <3043.157.182.194.141.1086621047.squirrel@www.csee.wvu.edu> (raw)
In-Reply-To: <40C3BC77.90106@specifixinc.com>
Hi Jim,
thank you very much for the information.it helps me a lot.and I have a
question regarding sampling time in gprof."how to change the sampling
time in gprof to get reasonable numbers in self seconds colomn ?"
sorry for asking this here but i didn't get any reply from the glibc
people.please tell me if u have idea about this.
best regards,
nath
> perugupa@csee.wvu.edu wrote:
>> builtins.c
>
> built-in function support. Used by several language front ends,
> primarly C/C++.
>
>> collect2.c
>
> Linker front-end for things like C++ static constructors/destructors,
> template repositories. Not used by all targets. Should be considered
> part of gcc driver.
>
>> cfgbuild.c
>
> Builds a cfg. Infrastructure used by a number of optimization passes.
>
>> enquire.c
>
> Build time only, not part of gcc binary. Produces FP constants
> suitable for float.h header file. No longer used, except possibly for
> an initial port. Has since been deleted from code base.
>
>> diagnostic.c
>
> Prints diagnostics. Used in multiple places.
>
>> timevar.c
>
> Prints timing info used for simple gcc profiling. Part of compiler
> infrastructure.
>
>> sbitmap.c
>
> bitmap data structures. Part of infrastructure. Used in multiple
> places.
>
>> intl.c
>
> Internationalization code. Used in multiple places, anyplace that
> parses or prints strings.
>
>> linemap.c
>
> Tracks file names and line numbers. Used for printing diagnostics in
> the preprocessor.
>
>> mkdeps.c
>
> Makefile dependency generator. Used in preprocessor.
>
>> params.c
>
> Used for run-time controllable parameters, cf the --parm option.
> Infrastructure used in many optimization passes.
>
>> prefix.c
>
> Used for converting file name paths, intended for Windows registry
> support, but not really used by anyone. Infrastructure.
>
>> hash.c
>> hastab.c
>> hashtable.c
>
> hash table data structures. Infrastructure used in multiple places.
>
>> ggc-common.c
>> ggc-none.c
>> ggc-page.c
>
> gcc garbage collector for memory management. Infrastructure, used in
> multiple places.
> --
> Jim Wilson, GNU Tools Support, http://www.SpecifixInc.com
next prev parent reply other threads:[~2004-06-07 15:11 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-01 17:05 perugupa
2004-06-07 0:53 ` Jim Wilson
2004-06-07 15:11 ` perugupa [this message]
2004-06-07 16:58 ` Jim Wilson
2004-06-13 19:32 ` where the compilation process stops in gcc perugupa
2004-06-24 16:42 ` Jim Wilson
2004-06-26 19:13 ` perugupa
2004-06-28 11:15 ` Dave Korn
2004-06-28 18:04 ` Jim Wilson
-- strict thread matches above, loose matches on Subject: below --
2004-05-10 15:18 HELP: GCC Passes and Files perugupa
2004-05-14 1:21 ` Jim Wilson
[not found] ` <2861.157.182.194.86.1084812450.squirrel@www.csee.wvu.edu>
[not found] ` <1084818403.1072.25.camel@leaf.tuliptree.org>
2004-05-21 16:26 ` perugupa
2004-05-21 17:04 ` Dave Korn
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=3043.157.182.194.141.1086621047.squirrel@www.csee.wvu.edu \
--to=perugupa@csee.wvu.edu \
--cc=gcc@gcc.gnu.org \
--cc=wilson@specifixinc.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).