public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Stefan Liebler <stli@linux.vnet.ibm.com>
To: libc-alpha@sourceware.org
Cc: Florian Weimer <fweimer@redhat.com>,
	"Paul E. Murphy" <murphyp@linux.vnet.ibm.com>,
	schwab@suse.de, "Joseph S. Myers" <joseph@codesourcery.com>
Subject: [PING][PATCH v3 1/9] Add configure check to test if gcc supports attribute ifunc.
Date: Mon, 05 Sep 2016 07:13:00 -0000	[thread overview]
Message-ID: <e866b188-7e43-518a-a466-3e740b73d4d9@linux.vnet.ibm.com> (raw)
In-Reply-To: <1472047472-30307-1-git-send-email-stli@linux.vnet.ibm.com>

On 08/24/2016 04:04 PM, Stefan Liebler wrote:
> This patch adds a configure check to test if gcc supports attribute ifunc.
> The support can either be enabled in <gcc-src>/gcc/config.gcc for one
> architecture in general by setting default_gnu_indirect_function variable to yes
> or by configuring gcc with --enable-gnu-indirect-function.
>
> The next patch rewrites libc_ifunc macro to use gcc attribute ifunc instead
> of inline assembly to generate the IFUNC symbols due to false debuginfo.
>
> If gcc does not support attribute ifunc, the old approach for generating
> ifunc'ed symbols is used. Then the debug-information is false. Thus it is
> recommended to use a gcc with indirect function support (See notes in INSTALL).
> After this patch-series these inline assemblies for ifunc-handling are not
> scattered in multiple files but are used only indirect via ifunc-macros
> and can simply removed in libc-symbols.h in future.
>
> If glibc is configured with --enable-multi-arch and gcc does not support
> attribute ifunc, a configure warning is dumped!
>
> This NEWS entry will be added:
> * For multi-arch support it is recommended to use a GCC with gnu-indirect-function
>   support as it is used to generate ifunc'ed symbols with correct
>   debug-information. This support can either be enabled by configuring GCC with
>   '--enable-gnu-indirect-function' or by enabling it by default by setting
>   'default_gnu_indirect_function' variable for a particular architecture in
>   gcc source file 'gcc/config.gcc'.
>
> ChangeLog:
>
> 	* config.h.in (HAVE_GCC_IFUNC): New undef.
> 	* configure.ac: Add check if gcc supports attribute ifunc feature.
> 	* configure: Regenerated.
> 	* manual/install.texi: Add recommendation for gcc with
> 	indirect-function support.
> 	* INSTALL: Regenerated.

Hi,

PING.

Here is the current status of the patchset:
-"[PATCH v3 1/9] Add configure check to test if gcc supports attribute 
ifunc.":
ok from Florian.

-"[PATCH v3 2/9] Use gcc attribute ifunc in libc_ifunc macro instead of 
inline assembly due to false debuginfo.":
partial ok from Paul. Paul, are the redirection of the f/l variants of 
__finite and others ok as they are needed (see my previous answer)?
PING: ifunc-macros in libc-symbols.h

-"[PATCH v3 3/9] s390: Refactor ifunc resolvers due to false debuginfo.":
PING.

-"[PATCH v3 4/9] i386, x86: Use libc_ifunc macro for time, gettimeofday.":
PING. Andreas, are the names for the redirection defines okay?

-"[PATCH v3 5/9] ppc: Use libc_ifunc macro for time, gettimeofday.":
ok from Paul.

-"[PATCH v3 6/9] Use libc_ifunc macro for clock_* symbols in librt.":
ok from Florian.

-"[PATCH v3 7/9] Use libc_ifunc macro for system in libpthread.":
ok from Florian.

-"[PATCH v3 8/9] Use libc_ifunc macro for vfork in libpthread.":
ok from Florian.

-"[PATCH v3 9/9] Use libc_ifunc macro for siglongjmp, longjmp in 
libpthread.":
PING.

Bye.
Stefan

  parent reply	other threads:[~2016-09-05  7:13 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-24 14:05 [PATCH " Stefan Liebler
2016-08-24 14:05 ` [PATCH v3 2/9] Use gcc attribute ifunc in libc_ifunc macro instead of inline assembly due to false debuginfo Stefan Liebler
2016-08-29 20:16   ` Paul E. Murphy
2016-08-30 14:12     ` Stefan Liebler
2016-09-29 18:38   ` Adhemerval Zanella
2016-09-30 13:45     ` Stefan Liebler
2016-10-04 13:14       ` Adhemerval Zanella
2016-08-24 14:05 ` [PATCH v3 3/9] s390: Refactor ifunc resolvers " Stefan Liebler
2016-08-30 12:31   ` Florian Weimer
2016-08-30 14:12     ` Stefan Liebler
2016-08-24 14:05 ` [PATCH v3 8/9] Use libc_ifunc macro for vfork in libpthread Stefan Liebler
2016-08-30 12:40   ` Florian Weimer
2016-08-24 14:05 ` [PATCH v3 9/9] Use libc_ifunc macro for siglongjmp, longjmp " Stefan Liebler
2016-10-06 11:59   ` Florian Weimer
2016-08-24 14:05 ` [PATCH v3 6/9] Use libc_ifunc macro for clock_* symbols in librt Stefan Liebler
2016-08-30 12:39   ` Florian Weimer
2016-08-24 14:05 ` [PATCH v3 5/9] ppc: Use libc_ifunc macro for time, gettimeofday Stefan Liebler
2016-08-30 13:46   ` Paul E. Murphy
2016-08-24 14:05 ` [PATCH v3 4/9] i386, x86: " Stefan Liebler
2016-09-29 14:34   ` Andreas Schwab
2016-08-24 17:02 ` [PATCH v3 7/9] Use libc_ifunc macro for system in libpthread Stefan Liebler
2016-08-30 12:39   ` Florian Weimer
2016-08-29  9:34 ` [PATCH v3 1/9] Add configure check to test if gcc supports attribute ifunc Florian Weimer
2016-08-30 14:12   ` Stefan Liebler
2016-09-05  7:13 ` Stefan Liebler [this message]
2016-09-29 13:50   ` [PING][PATCH " Stefan Liebler
2016-10-07  9:19 ` [PATCH " Stefan Liebler

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=e866b188-7e43-518a-a466-3e740b73d4d9@linux.vnet.ibm.com \
    --to=stli@linux.vnet.ibm.com \
    --cc=fweimer@redhat.com \
    --cc=joseph@codesourcery.com \
    --cc=libc-alpha@sourceware.org \
    --cc=murphyp@linux.vnet.ibm.com \
    --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).