- To: Renata Hodovan <hodovan@xxxxxxxxxxxxxxx>
- Subject: Re: Question about instrumenting gcc
- From: Ian Lance Taylor <iant@xxxxxxxxxx>
- Date: Tue, 12 Jun 2012 09:41:53 -0700
- Cc: gcc-help@xxxxxxxxxxx
- Comment: DKIM? See http://www.dkim.org
- Comment: DomainKeys? See http://antispam.yahoo.com/domainkeys
- In-reply-to: <4FD74016.4020803@inf.u-szeged.hu> (Renata Hodovan's message of "Tue, 12 Jun 2012 15:11:50 +0200")
- User-agent: Gnus/5.13 (Gnus v5.13) Emacs/23.1 (gnu/linux)
Renata Hodovan <hodovan@xxxxxxxxxxxxxxx> writes:
> thank you very much your help. I redesigned __cyg_profile_enter and
> __cyg_profile_exit functions and I stay in the right memory
> interval. Furthermore I'm using now main_constructor and
> main_destructor instead of start_test and end_test. The settings of
> make also seem good, it creates the output of instrumentation that way
> what I expected. But the compilation failed after a point because it
> couldn't understand e.g. size_t in filenames.h and a lot of similar
> errors in files what I haven't touched. I thought, since I add file IO
> operations to the main.c or linking the instrument file to the
> project, I distracted somehow the dependency. At this point I tried to
> compile the gcc --disable-bootstrap but then the instrumentation flag
> hadn't any results. What is the problem now? :S
When you configure with --disable-bootstrap, use CFLAGS rather than
BOOT_CFLAGS. BOOT_CFLAGS only applies to stages 2 and 3.
I have no idea what the problem is when bootstrapping. You would need
to provide more information.
Ian
[Linux C Programming]
[Linux Kernel]
[eCos]
[Fedora Development]
[Fedora Announce]
[Autoconf]
[The DWARVES Debugging Tools]
[Yosemite Campsites]
[Yosemite News]
[Linux GCC]