aboutsummaryrefslogtreecommitdiff
path: root/NEWS
diff options
context:
space:
mode:
authorSiddhesh Poyarekar <siddhesh@redhat.com>2013-12-03 12:26:12 +0530
committerSiddhesh Poyarekar <siddhesh@redhat.com>2013-12-03 12:26:12 +0530
commit520d437b9455560d099fe6bd9664be1f9f76868b (patch)
tree9c5ced695b6a5641628c702d7cc26b375e42004b /NEWS
parent416e014536950a77183013fa4c86cb42dfd322a9 (diff)
downloadglibc-520d437b9455560d099fe6bd9664be1f9f76868b.tar
glibc-520d437b9455560d099fe6bd9664be1f9f76868b.tar.gz
glibc-520d437b9455560d099fe6bd9664be1f9f76868b.tar.bz2
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 'NEWS')
-rw-r--r--NEWS4
1 files changed, 2 insertions, 2 deletions
diff --git a/NEWS b/NEWS
index e85b4c6e30..c431d72539 100644
--- a/NEWS
+++ b/NEWS
@@ -19,8 +19,8 @@ Version 2.19
15892, 15893, 15895, 15897, 15905, 15909, 15917, 15919, 15921, 15923,
15939, 15948, 15963, 15966, 15985, 15988, 15997, 16032, 16034, 16036,
16037, 16041, 16055, 16071, 16072, 16074, 16077, 16078, 16103, 16112,
- 16143, 16144, 16146, 16150, 16151, 16153, 16167, 16172, 16214, 16245,
- 16271.
+ 16143, 16144, 16146, 16150, 16151, 16153, 16167, 16172, 16195, 16214,
+ 16245, 16271.
* The public headers no longer use __unused nor __block. This change is to
support compiling programs that are derived from BSD sources and use