Changes in 'finstrument-functions' option

2005-06-02 Thread Perret Yannick
Hi all, some times ago I wrote about a modification of the '-finstrument-functions' option of 'gcc'. My goal was (and is still) to obtain additionnal informations about functions (as symbols addresses is sometime not enough). So I made a patch to allow to send more data to the __cyg_profile_func

'main' enters in gcc-4.1

2005-07-07 Thread Perret Yannick
Hello, I'm using '-finstrument-functions' for a while to make function-level profiling. Recently, I compiled gcc-4.1 (without problem) and used it for the same purpose. Here is the result : Enter main (essai.c:41) [0x80490b0] from 0x4003be36 - PID=1774 - elaps=0 Enter main (essai.c:41) [0x8049

'main' enters in gcc-4.1

2005-07-11 Thread Perret Yannick
(second send, as I never saw my first send on the mailing list. sorry if duplicated). Hello, I'm using '-finstrument-functions' for a while to make function-level profiling. Recently, I compiled gcc-4.1 (without problem) and used it for the same purpose. Here is the result : >>> Enter main (es

Re: coding style: type* variable or type *varible

2005-09-14 Thread Perret Yannick
Dave Korn wrote: Original Message From: Mike Stump Sent: 13 September 2005 20:28 On Sep 13, 2005, at 12:23 PM, Rafael EspĂ­ndola wrote: I have seen both in gcc. I have found that "type* variable" is preferred in C++ code but I haven't found any guidelines for C code