From: mathieu.desnoyers@efficios.com (Mathieu Desnoyers)
Subject: [lttng-dev] Using userspace tracepoints with icc
Date: Fri, 8 Nov 2013 13:55:46 +0000 (UTC) [thread overview]
Message-ID: <246183477.63073.1383918946763.JavaMail.zimbra@efficios.com> (raw)
In-Reply-To: <527C6D8D.1010103@gmail.com>
----- Original Message -----
> From: "Rapha?l Beamonte" <raphael.beamonte@gmail.com>
> To: lttng-dev at lists.lttng.org
> Sent: Thursday, November 7, 2013 11:50:21 PM
> Subject: [lttng-dev] Using userspace tracepoints with icc
>
> Hello folks,
>
> A few weeks ago, I was working on an application which used icc (the
> Intel C Compiler) to compile its sources. I wanted to trace it but
> wasn't able to compile with the tracepoints, the ".c" file was spawning
> a ": internal error: backend signal" from icc. Still, there is a
> workaround to be able to trace.
>
> Using gcc to compile the tracepoints (or using the object file generated
> by lttng-gen-tp, which uses gcc) and linking the object file to the
> application worked like a charm. It is not the best way as it forces to
> use two different compilers, but it still allows to trace.
>
> Just thought I'd share this workaround if someone else search how to use
> LTTng-UST with icc.
You might want to report this internal compiler error to the Intel folks responsible for icc.
Thanks,
Mathieu
>
> Rapha?l
>
>
> _______________________________________________
> lttng-dev mailing list
> lttng-dev at lists.lttng.org
> http://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev
>
--
Mathieu Desnoyers
EfficiOS Inc.
http://www.efficios.com
prev parent reply other threads:[~2013-11-08 13:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-08 4:50 Raphaël Beamonte
2013-11-08 13:55 ` Mathieu Desnoyers [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=246183477.63073.1383918946763.JavaMail.zimbra@efficios.com \
--to=mathieu.desnoyers@efficios.com \
/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