From: "Dominique d'Humières" <dominiq@lps.ens.fr>
To: andi@firstfloor.org
Cc: gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PING^3] Re: [PATCH 1/3] Support instrumenting returns of instrumented functions
Date: Sun, 02 Dec 2018 16:26:00 -0000 [thread overview]
Message-ID: <E3C52DE1-412B-4190-B883-9903C11C1144@lps.ens.fr> (raw)
Hi Andi,
% gcc9 -S -pg -mfentry -minstrument-return=call -mrecord-return /opt/gcc/work/gcc/testsuite/gcc.target/i386/returninst1.c -m32
cc1: sorry, unimplemented: -mfentry isn't supported for 32-bit in combination with -fpic
The tests should be protected.
TIA
Dominique
next reply other threads:[~2018-12-02 16:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-02 16:26 Dominique d'Humières [this message]
2018-12-02 21:11 ` Andi Kleen
-- strict thread matches above, loose matches on Subject: below --
2018-11-05 0:02 Andi Kleen
2018-11-08 17:11 ` [PING] " Andi Kleen
2018-11-15 19:03 ` [PING^2] " Andi Kleen
2018-11-21 20:48 ` [PING^3] " Andi Kleen
2018-11-28 15:59 ` Jan Hubicka
2018-11-28 16:11 ` Andi Kleen
2018-11-28 16:24 ` Jan Hubicka
2018-11-28 20:47 ` Andi Kleen
2018-11-29 22:31 ` Jan Hubicka
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=E3C52DE1-412B-4190-B883-9903C11C1144@lps.ens.fr \
--to=dominiq@lps.ens.fr \
--cc=andi@firstfloor.org \
--cc=gcc-patches@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).