From: Florian Weimer <fweimer@redhat.com>
To: Andreas Schwab <schwab@suse.de>
Cc: GNU C Library <libc-alpha@sourceware.org>
Subject: Re: [PATCH] Test for profiling support (_mcount/gprof)
Date: Wed, 16 Aug 2017 15:32:00 -0000 [thread overview]
Message-ID: <357353c9-2633-a1a5-4d78-49862087a8a5@redhat.com> (raw)
In-Reply-To: <mvmy3qjr0m2.fsf@suse.de>
On 08/16/2017 05:30 PM, Andreas Schwab wrote:
> On Aug 16 2017, Florian Weimer <fweimer@redhat.com> wrote:
>
>> On 08/16/2017 05:20 PM, Andreas Schwab wrote:
>>> On Aug 16 2017, Florian Weimer <fweimer@redhat.com> wrote:
>>>
>>>> If you don't use --enable-frame-pointer for GCC, there's no apparent
>>>> reason to me to build glibc with --fomit-frame-pointer because it's the
>>>> default (albeit in a fashion that is compatible with -pg).
>>>
>>> That is not true.
>>
>> It is currently true—I don't see why anyone would want to build glibc
>> this way. Could you enlighten me?
>
> To omit the frame pointer.
But GCC does it by default if you don't build with
--enable-frame-pointer, at least on i386, which is the architecture for
which you reported the failure.
Thanks,
Florian
next prev parent reply other threads:[~2017-08-16 15:32 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-15 12:05 Florian Weimer
2017-08-15 12:29 ` Andreas Schwab
2017-08-15 12:46 ` Florian Weimer
2017-08-15 12:56 ` Andreas Schwab
2017-08-15 13:04 ` Florian Weimer
2017-08-15 13:34 ` Andreas Schwab
2017-08-15 14:18 ` Florian Weimer
2017-08-15 16:32 ` Joseph Myers
2017-08-15 16:40 ` Florian Weimer
2017-08-15 16:53 ` Joseph Myers
2017-08-16 6:46 ` Andreas Schwab
2017-08-16 7:07 ` Florian Weimer
2017-08-16 7:52 ` Andreas Schwab
2017-08-16 8:09 ` Florian Weimer
2017-08-16 8:42 ` Szabolcs Nagy
2017-08-16 15:05 ` Andreas Schwab
2017-08-16 15:07 ` Florian Weimer
2017-08-16 15:20 ` Andreas Schwab
2017-08-16 15:28 ` Florian Weimer
2017-08-16 15:31 ` Andreas Schwab
2017-08-16 15:32 ` Florian Weimer [this message]
2017-08-16 20:03 ` H.J. Lu
2017-08-16 21:04 ` Florian Weimer
2017-08-16 21:11 ` H.J. Lu
2017-08-16 21:19 ` H.J. Lu
2017-08-17 7:44 ` Florian Weimer
2017-08-17 11:57 ` H.J. Lu
2017-08-17 6:36 ` Andreas Schwab
2017-10-05 10:52 ` Florian Weimer
2017-10-05 12:19 ` Andreas Schwab
2017-10-05 12:21 ` Florian Weimer
2017-10-05 12:31 ` Andreas Schwab
2017-10-05 12:38 ` Florian Weimer
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=357353c9-2633-a1a5-4d78-49862087a8a5@redhat.com \
--to=fweimer@redhat.com \
--cc=libc-alpha@sourceware.org \
--cc=schwab@suse.de \
/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).