http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54926
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|REOPENED |WAITING
CC| |jakub at gcc dot gnu.org
--- Comment #7 from Jakub Jelinek <jakub at gcc dot gnu.org> 2012-12-06
18:39:03 UTC ---
For the bootstrap comparison failures, I'd guess libbacktrace should be built
with
-frandom-seed=$@
in CFLAGS similarly how libstdc++-v3 is built.
In what way doesn't backtrace work in the compiler? Does it crash, or not
print any backtrace? The former would be a regression, the latter would not.
So, does:
2012-12-06 Jakub Jelinek <[email protected]>
PR bootstrap/54926
* Makefile.am (AM_CFLAGS): Add -frandom-seed=$@.
* Makefile.in: Regenerated.
--- libbacktrace/Makefile.am.jj 2012-10-02 15:36:21.000000000 +0200
+++ libbacktrace/Makefile.am 2012-12-06 19:36:05.888001803 +0100
@@ -34,7 +34,7 @@ ACLOCAL_AMFLAGS = -I .. -I ../config
AM_CPPFLAGS = -I $(top_srcdir)/../include -I $(top_srcdir)/../libgcc \
-I ../libgcc -I ../gcc/include -I $(MULTIBUILDTOP)../../gcc/include
-AM_CFLAGS = $(EXTRA_FLAGS) $(WARN_FLAGS) $(PIC_FLAG)
+AM_CFLAGS = $(EXTRA_FLAGS) $(WARN_FLAGS) $(PIC_FLAG) -frandom-seed=$@
noinst_LTLIBRARIES = libbacktrace.la
--- libbacktrace/Makefile.in.jj 2012-10-02 15:36:21.000000000 +0200
+++ libbacktrace/Makefile.in 2012-12-06 19:36:26.284875521 +0100
@@ -254,7 +254,7 @@ ACLOCAL_AMFLAGS = -I .. -I ../config
AM_CPPFLAGS = -I $(top_srcdir)/../include -I $(top_srcdir)/../libgcc \
-I ../libgcc -I ../gcc/include -I $(MULTIBUILDTOP)../../gcc/include
-AM_CFLAGS = $(EXTRA_FLAGS) $(WARN_FLAGS) $(PIC_FLAG)
+AM_CFLAGS = $(EXTRA_FLAGS) $(WARN_FLAGS) $(PIC_FLAG) -frandom-seed=$@
noinst_LTLIBRARIES = libbacktrace.la
libbacktrace_la_SOURCES = \
backtrace.h \
patch fix all the regressions, turning this just into enhancement request to
support libbacktrace better on HP-UX?
