public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/52544] compilation fails with -finstrument-functions and sse c code
Date: Tue, 24 Jul 2012 09:30:00 -0000	[thread overview]
Message-ID: <bug-52544-4-CgkLGRUetq@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-52544-4@http.gcc.gnu.org/bugzilla/>

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

Richard Guenther <rguenth at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |NEW
   Last reconfirmed|                            |2012-07-24
                 CC|                            |hubicka at gcc dot gnu.org
     Ever Confirmed|0                           |1

--- Comment #3 from Richard Guenther <rguenth at gcc dot gnu.org> 2012-07-24 09:30:14 UTC ---
Confirmed.  It's because we instrument before inlining always-inline functions
and get calls like

  __cyg_profile_func_enter (_mm_set1_ps, return_addr.3_22);

but of course no body for _mm_set1_ps function exists (not should it, IMHO).
We do the instrumentation during gimplification.

Honza, why does the address-taking of _mm_set1_ps not force its body
to be output?  Is there a predicate we can check that tells us wheter
a function body will forcefully _not_ be output?  Add that to

void
gimplify_function_tree (tree fndecl)
{
...
  /* If we're instrumenting function entry/exit, then prepend the call to
     the entry hook and wrap the whole function in a TRY_FINALLY_EXPR to
     catch the exit hook.  */
  /* ??? Add some way to ignore exceptions for this TFE.  */
  if (flag_instrument_function_entry_exit
      && !DECL_NO_INSTRUMENT_FUNCTION_ENTRY_EXIT (fndecl)
      && !flag_instrument_functions_exclude_p (fndecl))
    {


  parent reply	other threads:[~2012-07-24  9:30 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-09 17:30 [Bug c/52544] New: " jgpiccinali at free dot fr
2012-03-10  7:51 ` [Bug middle-end/52544] " pinskia at gcc dot gnu.org
2012-07-23 14:47 ` oeste.sebastian at googlemail dot com
2012-07-23 14:50 ` oeste.sebastian at googlemail dot com
2012-07-24  9:30 ` rguenth at gcc dot gnu.org [this message]
2013-06-28 13:45 ` rodrigo at sdfg dot com.ar
2013-06-28 15:25 ` rodrigo at sdfg dot com.ar
2013-08-13  8:17 ` rodrigo at sdfg dot com.ar
2014-12-20 14:44 ` mobi at mobiphil dot com
2014-12-20 14:58 ` mobi at mobiphil dot com

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=bug-52544-4-CgkLGRUetq@http.gcc.gnu.org/bugzilla/ \
    --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).