Blame SOURCES/gcc8-rh1574936.patch

0e3697
crt files and statically linked libgcc objects cause false positives
0e3697
in annobin coverage, so we add the assembler flag to generate notes
0e3697
for them.
0e3697
0e3697
The patch also adds notes to libgcc_s.so, but this is harmless because
0e3697
these notes only confer that there is no other annobin markup.
0e3697
0e3697
2018-07-25  Florian Weimer  <fweimer@redhat.com>
0e3697
0e3697
	* Makefile.in (LIBGCC2_CFLAGS, CRTSTUFF_CFLAGS): Add
0e3697
	-Wa,--generate-missing-build-notes=yes.
0e3697
0e3697
--- libgcc/Makefile.in	2018-01-13 13:05:41.000000000 +0100
0e3697
+++ libgcc/Makefile.in	2018-07-25 13:15:02.036226940 +0200
0e3697
@@ -244,6 +244,7 @@
0e3697
 LIBGCC2_CFLAGS = -O2 $(LIBGCC2_INCLUDES) $(GCC_CFLAGS) $(HOST_LIBGCC2_CFLAGS) \
0e3697
 		 $(LIBGCC2_DEBUG_CFLAGS) -DIN_LIBGCC2 \
0e3697
 		 -fbuilding-libgcc -fno-stack-protector \
0e3697
+		 -Wa,--generate-missing-build-notes=yes \
0e3697
 		 $(INHIBIT_LIBC_CFLAGS)
0e3697
 
0e3697
 # Additional options to use when compiling libgcc2.a.
0e3697
@@ -297,6 +298,7 @@
0e3697
   $(NO_PIE_CFLAGS) -finhibit-size-directive -fno-inline -fno-exceptions \
0e3697
   -fno-zero-initialized-in-bss -fno-toplevel-reorder -fno-tree-vectorize \
0e3697
   -fbuilding-libgcc -fno-stack-protector $(FORCE_EXPLICIT_EH_REGISTRY) \
0e3697
+  -Wa,--generate-missing-build-notes=yes \
0e3697
   $(INHIBIT_LIBC_CFLAGS)
0e3697
 
0e3697
 # Extra flags to use when compiling crt{begin,end}.o.
0e3697