public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
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: Thu, 05 Oct 2017 10:52:00 -0000	[thread overview]
Message-ID: <479c33cb-62a2-4b56-8908-8adc0fd18a2a@redhat.com> (raw)
In-Reply-To: <907f751a-3916-64c9-f650-df182fb3cdce@redhat.com>

On 08/16/2017 10:09 AM, Florian Weimer wrote:
> tst-gmon: Build with -fno-omit-frame-pointer
> 
> If glibc is built with -fomit-frame-pointer to undo the effect of
> configuring GCC with --enable-frame-pointer, using -pg by itself results
> in a build failure:
> 
> gcc: error: -pg and -fomit-frame-pointer are incompatible
> 
> 2017-08-16  Florian Weimer<fweimer@redhat.com>
> 
> 	* gmon/Makefile (CFLAGS-tst-gmon.c): Add -fno-omit-frame-pointer.
> 
> diff --git a/gmon/Makefile b/gmon/Makefile
> index 39f11acec2..62d96543ff 100644
> --- a/gmon/Makefile
> +++ b/gmon/Makefile
> @@ -38,7 +38,7 @@ endif
>   # The mcount code won't work without a frame pointer.
>   CFLAGS-mcount.c := -fno-omit-frame-pointer
>   
> -CFLAGS-tst-gmon.c := -pg
> +CFLAGS-tst-gmon.c := -fno-omit-frame-pointer -pg
>   LDFLAGS-tst-gmon := $(no-pie-ldflag)
>   CRT-tst-gmon := $(csu-objpfx)gcrt1.o
>   tst-gmon-ENV := GMON_OUT_PREFIX=$(objpfx)tst-gmon.data

Is this patch still needed?

Thanks,
Florian

  parent reply	other threads:[~2017-10-05 10:52 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
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 [this message]
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=479c33cb-62a2-4b56-8908-8adc0fd18a2a@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).