should appchk know about STT_GNU_IFUNC

In bug 2722, it is reported that libchk misses some symbols in glibc 2.10.
This turns out to be do to the new switching code using STT_GNU_IFUNC symbol
entries introduced in recent toolchains. The purpose is for the dynamic linker
to be able to select an appropriate routine based on known architectural
(optimization, etc.) needs at runtime. libchk has been taught about this,
which when appearing in system libraries can be considered an implementation
detail.

It was decided to split off as a separate question what should be done on the
application side:

(a) is there any impact on application binaries, and if so, does that have to
be allowed since likely older dynamic linkers on conforming systems can't
handle such types

(b) what should be done with application-provided shared libraries
[reply] [-] Comment 1