From b6a6df4a0de194eeec4e3f5f91d2874309814e59 Mon Sep 17 00:00:00 2001
From: Thomas Schwinge <thomas@codesourcery.com>
Date: Wed, 7 Dec 2016 17:36:36 +0100
Subject: binutils-gdb: 03b62bbbce3dc5f15131d9e78f77d035cd1cffb3 (2016-11-23)

---
 open_issues/binutils.mdwn | 12 ++++++------
 1 file changed, 6 insertions(+), 6 deletions(-)

(limited to 'open_issues')

diff --git a/open_issues/binutils.mdwn b/open_issues/binutils.mdwn
index 9a3ead9e..328cc24b 100644
--- a/open_issues/binutils.mdwn
+++ b/open_issues/binutils.mdwn
@@ -47,7 +47,7 @@ git diff --patience --stat=$COLUMNS,$COLUMNS --patch --src-prefix=./ --dst-prefi
 
 -->
 
-Last reviewed up to Git commit b593ecca856860a8b38deb808493bba4beef3aee
+Last reviewed up to Git commit 03b62bbbce3dc5f15131d9e78f77d035cd1cffb3
 (2016-11-23).
 
   * Globally
@@ -405,7 +405,7 @@ Last reviewed up to Git commit b593ecca856860a8b38deb808493bba4beef3aee
 # Build
 
 Here's a log of a binutils-gdb build run; this is from Git commit
-b593ecca856860a8b38deb808493bba4beef3aee (2016-11-23),
+03b62bbbce3dc5f15131d9e78f77d035cd1cffb3 (2016-11-23),
 plus `PATH_MAX` hard-coded in `gdb/inferior.c` and `gdb/remote.c`,
 and `global_thread_id_to_ptid` used instead of
 `thread_id_to_pid` in `gdb/gnu-nat.c`,
@@ -425,7 +425,7 @@ so we need to configure with support for plugins and
 sysroots.  In the GDB build, there are compiler diagnostics reported in the
 MIG-generated stub files; thus no `-Werror` until that is resolved.
 
-This takes up around 1.8 GiB, and runs for [[24 min|performance#measure]] on
+This takes up around 1.8 GiB, and runs for [[25 min|performance#measure]] on
 kepler.SCHWINGE and [[25 min|performance#measure]] on laplace.SCHWINGE.
 
 <!--
@@ -543,8 +543,8 @@ formats, and more emulation vectors.
     $ make install 2>&1 | tee log_install
     [...]
 
-This takes up around 270 MiB, and runs for [[1 min|performance#measure]] on
-kepler.SCHWINGE and [[2 min|performance#measure]] on laplace.SCHWINGE.
+This takes up around 270 MiB, and runs for [[0 min|performance#measure]] on
+kepler.SCHWINGE and [[1 min|performance#measure]] on laplace.SCHWINGE.
 
 
 ## Analysis
@@ -570,7 +570,7 @@ so instead we apply an ugly hack to `gold/testsuite/Makefile`.
     $ make -k check RUNTESTFLAGS=CC_FOR_TARGET='gcc-6\ -fno-pie\ -fno-PIE\ -no-pie'\ CXX_FOR_TARGET='g++-6\ -fno-pie\ -fno-PIE\ -no-pie' CC_FOR_TARGET='gcc-6 -fno-pie -fno-PIE -no-pie' CXX_FOR_TARGET='g++-6 -fno-pie -fno-PIE -no-pie' 2>&1 | tee log_test
     [...]
 
-This runs for [[25 min|performance#measure]] on kepler.SCHWINGE and [[68
+This runs for [[25 min|performance#measure]] on kepler.SCHWINGE and [[71
 min|performance#measure]] on laplace.SCHWINGE.
 
 When running `make -k check 2>&1 | tee log_test`, at the end of the testsuite
-- 
cgit v1.2.3