public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rodrigo at sdfg dot com.ar" <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: Fri, 28 Jun 2013 13:45:00 -0000	[thread overview]
Message-ID: <bug-52544-4-QaXlMasfsM@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

Rodrigo Campos <rodrigo at sdfg dot com.ar> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |rodrigo at sdfg dot com.ar

--- Comment #4 from Rodrigo Campos <rodrigo at sdfg dot com.ar> ---
I think I'm hitting a similar issue, although not when using sse code in my
case.

I'm working on a (shared) library that uses P99: http://p99.gforge.inria.fr/. I
just use it as a git submodule on commit 59e08b2, so not linking nor anything
"wierd" there, just as it was part of my source code.

When I compile the shared library, of course, no error is thrown. But when I
try to link agains it, the same "undefined reference to" error to a bunch of
P99 functions. For example something like this is shown:

./liborwl.so: undefined reference to `mtx_lock'
./liborwl.so: undefined reference to `p99_count_destroy'
./liborwl.so: undefined reference to `p99_rand'


Lot of them, I didn't check all, have the "always_inline". And some also have
the "warn_unused_result" gcc attribute or something else.

Also, I'm using gcc 4.7.2 (in debian stable). If I use gcc 4.5 the code
compiles and link okay, but when I run the executable it seems there is a
memory corruption and nothing works as expected.

Is this "-finstrument-function" flag still supported ?




Thanks a lot,
Rodrigo


  parent reply	other threads:[~2013-06-28 13:45 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
2013-06-28 13:45 ` rodrigo at sdfg dot com.ar [this message]
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-QaXlMasfsM@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).