[fpc-pascal] fpc and intel vtune (now about gprof)

Tomas Hajny XHajT03 at mbox.vol.cz
Tue Apr 25 13:40:23 CEST 2006


đŁÔŇ ëĎÓÁŇĹ×ÓËÉĘ wrote:
> Sorry, eight questions ahead (first two are important to me).
 .
 .
>> Last time I used gprof on win32, it worked fine?
>
> Well, not long ago I was told in these maillists, that gprof requires
> cygwin under win32 for FPC.
>
> Is it normal, that compiler (linking stage) tells: "...ld.exe: cannot find
> -lc" and fails? (I thought about installing cygwin, but I don't understand
> what do I need from it.)

Just guessing here: Most probably libc.dll? Better to be answered by
someone else.


> Is it supposed, that I integrate cygwin with FPC or something?

No, except that you have to provide its runtime libraries.


> Is it normal, that FPC from almost fresh base_w32... and
> fpc-2.0.3.i386-win32... required "as.exe" and "ld.exe" (I copied them from
> slightly older ones)?

I'd say so - if you're talking about snapshots, these tools are not
included in them (as opposed to releases).


> Is it OK, that after recent FPC update I have to add "-Sg" for my pretty
> GOTO (It is objfpc mode, no extra option is required under Delphi)?

Use -Mdelphi (or {MODE DELPHI}) if you want compatibility to Delphi. Use
of GOTO (and some other constructs supported by Delphi) isn't considered a
good programming practice, so it isn't supported by default in native FPC
modes. If you want to use GOTO in these modes, you need to supply -Sg
explicitely.


> Is it normal, that with e.g. "-va" switch I see verbosely what was
> processed before "-va" switch?

I'm not sure if I understand what you meant here?


> Should I bump the "fixed" bug about uncommented compiler option "-Op4" (it
> is uncommented in both 2.0.3 and 2.1.x versions)?

I guess it would help to be more specific here - what exactly is wrong,
please?


> Is it sufficient to build 2.1.x and rename one of "fpc.exe" to operate
> both release and development versions (I didn't try, but it seems that the
> one ppc386 would be run)?

That depends. It could work if you provide proper fpc.cfg in the compiler
directory (and no other fpc.cfg exists in other directories) and if you
make sure to use different output directories for compilation of your own
units.


> Should I split this message?

Not necessarily if you don't mind receiving answers in many pieces
(different people responding to different parts). ;-)

Regards

Tomas




More information about the fpc-pascal mailing list