diff options
author | Siddhesh Poyarekar <siddhesh@redhat.com> | 2013-12-03 12:26:12 +0530 |
---|---|---|
committer | Siddhesh Poyarekar <siddhesh@redhat.com> | 2013-12-03 12:26:12 +0530 |
commit | 520d437b9455560d099fe6bd9664be1f9f76868b (patch) | |
tree | 9c5ced695b6a5641628c702d7cc26b375e42004b /iconvdata | |
parent | 416e014536950a77183013fa4c86cb42dfd322a9 (diff) | |
download | glibc-520d437b9455560d099fe6bd9664be1f9f76868b.tar.gz glibc-520d437b9455560d099fe6bd9664be1f9f76868b.tar.xz glibc-520d437b9455560d099fe6bd9664be1f9f76868b.zip |
[BZ #16195] Fix build warnings from systemtap probes in non-systemtap configurations
Joseph pointed out in the bug report (and in an earlier thread) that systemtap probes cause build time warnings like the following: ../sysdeps/ieee754/dbl-64/e_atan2.c:602:4: warning: the address of 'p' will always evaluate as 'true' [-Waddress] due to the fact that we're now passing non-weak variables to LIBC_PROBE in the libm probes. This happens only on configurations that do not enable systemtap. The macro definition of LIBC_PROBE in this case only acts as a sanity checker to ensure that the number parameters passed to LIBC_PROBE is equal to the argument count parameter passed before it. This can be done in a much simpler manner by just adding a macro definition for each number of arguments. I am assuming here that we don't really want to bother with supporting LIBC_PROBE with an indeterminate number of arguments and if there is a need for a probe to have more data than what is currently supported (4 arguments), one could simply add an additional macro here.
Diffstat (limited to 'iconvdata')
0 files changed, 0 insertions, 0 deletions