public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "andreas dot knuepfer at tu-dresden dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/28205] Request an option to make -finstrument-functions not apply to inlined function calls
Date: Fri, 06 Oct 2006 12:40:00 -0000	[thread overview]
Message-ID: <20061006124026.16624.qmail@sourceware.org> (raw)
In-Reply-To: <bug-28205-12892@http.gcc.gnu.org/bugzilla/>



------- Comment #3 from andreas dot knuepfer at tu-dresden dot de  2006-10-06 12:40 -------
Would it be feasible to pass a different function address for inlined
functions? In particular, it should not be the same address as the parent
function. 

I seem to recall that in previous versions (2.95.x, 3.x) of GCC
__cyg_profile_func_enter() used the call location of an inlined function as 
first argument. 
This is somewhere in the middle of the parent function, which makes sense
somehow. Any invalid address could be used as well.
In the end, the user could be aware of a function being inlined.


-- 

andreas dot knuepfer at tu-dresden dot de changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |andreas dot knuepfer at tu-
                   |                            |dresden dot de


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=28205


      parent reply	other threads:[~2006-10-06 12:40 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-29 22:28 [Bug c++/28205] New: " joev dot dubach at nuance dot com
2006-07-03 18:01 ` [Bug middle-end/28205] " joev dot dubach at nuance dot com
2006-09-03  7:26 ` pinskia at gcc dot gnu dot org
2006-10-06 12:40 ` andreas dot knuepfer at tu-dresden dot de [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=20061006124026.16624.qmail@sourceware.org \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /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).