Index: head/en_US.ISO8859-1/htdocs/news/status/report-2017-07-2017-09.xml
===================================================================
--- head/en_US.ISO8859-1/htdocs/news/status/report-2017-07-2017-09.xml	(revision 51145)
+++ head/en_US.ISO8859-1/htdocs/news/status/report-2017-07-2017-09.xml	(revision 51146)
@@ -1,257 +1,314 @@
 <?xml version="1.0" encoding="utf-8" ?>
 <!DOCTYPE report PUBLIC "-//FreeBSD//DTD FreeBSD XML Database for
   Status Report//EN"
   "http://www.FreeBSD.org/XML/share/xml/statusreport.dtd" >
 
 <!-- $FreeBSD$ -->
 
 <!--
      Variables to replace:
      %%START%%     - report month start
      %%STOP%%      - report month end
      %%YEAR%%      - report year
      %%NUM%%       - report issue (first, second, third, fourth)
      %%STARTNEXT%% - report month start
      %%STOPNEXT%%  - report month end
      %%YEARNEXT%%  - next report due year (if different than %%YEAR%%)
      %%DUENEXT%%   - next report due date (i.e., June 6)
 -->
 
 <report>
   <date>
     <month>%%START%%-%%STOP%%</month>
 
     <year>%%YEAR%%</year>
   </date>
 
   <section>
     <title>Introduction</title>
 
     <p><strong>This is a draft of the %%START%%&ndash;%%STOP%% %%YEAR%%
       status report.  Please check back after it is finalized, and
       an announcement email is sent to the &os;-Announce mailing
       list.</strong></p>
 
     <?ignore
     <p>This report covers &os;-related projects between %%START%% and
       %%STOP%% %%YEAR%%.  This is the %%NUM%% of four reports planned for
       %%YEAR%%.</p>
 
     <p>The %%NUM%% quarter of %%YEAR%% was another productive quarter for
       the &os; project and community. [...]</p>
 
     <p>Thanks to all the reporters for the excellent work!</p>
 
     <p>The deadline for submissions covering the period from %%STARTNEXT%%
       to %%STOPNEXT%% %%YEARNEXT%% is %%DUENEXT%%, %%YEARNEXT%%.</p>
      ?>
   </section>
 
   <category>
     <name>team</name>
 
     <description>&os; Team Reports</description>
 
     <p>Entries from the various official and semi-official teams,
       as found in the <a href="&enbase;/administration.html">Administration
 	Page</a>.</p>
   </category>
 
   <category>
     <name>proj</name>
 
     <description>Projects</description>
 
     <p>Projects that span multiple categories, from the kernel and userspace
       to the Ports Collection or external projects.</p>
   </category>
 
   <category>
     <name>kern</name>
 
     <description>Kernel</description>
 
     <p>Updates to kernel subsystems/features, driver support,
       filesystems, and more.</p>
   </category>
 
   <category>
     <name>arch</name>
 
     <description>Architectures</description>
 
     <p>Updating platform-specific features and bringing in support
       for new hardware platforms.</p>.
   </category>
 
   <category>
     <name>bin</name>
 
     <description>Userland Programs</description>
 
     <p>Changes affecting the base system and programs in it.</p>
   </category>
 
   <category>
     <name>ports</name>
 
     <description>Ports</description>
 
     <p>Changes affecting the Ports Collection, whether sweeping
       changes that touch most of the tree, or individual ports
       themselves.</p>
   </category>
 
   <category>
     <name>doc</name>
 
     <description>Documentation</description>
 
     <p>Noteworthy changes in the documentation tree or new external
       books/documents.</p>
   </category>
 
   <category>
     <name>misc</name>
 
     <description>Miscellaneous</description>
 
     <p>Objects that defy categorization.</p>
   </category>
 
   <category>
     <name>third</name>
 
     <description>Third-Party Projects</description>
 
     <p>Many projects build upon &os; or incorporate components of
       &os; into their project.  As these projects may be of interest 
       to the broader &os; community, we sometimes include brief
       updates submitted by these projects in our quarterly report.
       The &os; project makes no representation as to the accuracy or
       veracity of any claims in these submissions.</p>
   </category>
 
   <project cat='team'>
     <title>&os; Release Engineering Team</title>
 
     <contact>
       <person>
 	<name>&os;&nbsp;Release Engineering Team</name>
 	<email>re@FreeBSD.org</email>
       </person>
     </contact>
 
     <links>
       <url href="https://www.FreeBSD.org/releases/11.1R/announce.html">&os;&nbsp;11.1-RELEASE Announcement</url>
       <url href="https://www.FreeBSD.org/releases/10.4R/schedule.html">&os;&nbsp;10.4-RELEASE Schedule</url>
       <url href="https://download.FreeBSD.org/ftp/snapshots/ISO-IMAGES/">&os; Development Snapshots</url>
     </links>
 
     <body>
       <p>The &os; Release Engineering Team is responsible for setting
 	and publishing release schedules for official project releases
 	of &os;, announcing code freezes, and maintaining the
 	respective branches, among other things.</p>
 
       <p>The &os; Release Engineering Team continued finalizing the
 	11.1-RELEASE cycle, with the final release builds starting on
 	July 21 and the official release announcement email sent on
 	July 26.  Thank you to everyone who helped test 11.1-RELEASE,
 	ensuring its quality and stability.&nbsp;[1]</p>
 
       <p>&os;&nbsp;11.1-RELEASE is the second release from the
 	<tt>stable/11</tt> branch.</p>
 
       <p>Additionally, the &os; Release Engineering Team started the
 	10.4-RELEASE cycle, with the code slush starting on July 28.
 	With the final release build expected to start on September 29
 	and the official announcement overlapping the end of the
 	quarter, everything is on schedule as of this
 	writing.&nbsp;[2]</p>
 
       <p>&os;&nbsp;10.4-RELEASE will be the fifth release from the
 	<tt>stable/10</tt> branch, and is planned to be the final release
 	of the 10.x series.</p>
     </body>
 
     <sponsor>The &os; Foundation&nbsp;[1]</sponsor>
 
     <partialsponsor>The &os; Foundation&nbsp;[2]</partialsponsor>
   </project>
 
   <project cat="arch">
     <title>AMD Zen (family 17h) support</title>
 
     <contact>
       <person>
 	<name>
 	  <given>Conrad</given>
 	  <common>Meyer</common>
 	  <email>cem@FreeBSD.org</email>
 	</name>
       </person>
     </contact>
 
     <body>
       <p>This quarter, a bit of work was done to enhance platform
 	support for AMD Zen (Ryzen, Threadripper, Epyc) processors:</p>
 
       <ul>
 	<li>The CPU topology detection code was enhanced to properly
 	  detect Zen dies and CCXes.  This gives the scheduler more
 	  locality information to make scheduling decisions.</li>
 
 	<li>The x86 topology analysis was enhanced to report dies and
 	  CCXes, in addition to the existing reporting on packages,
 	  cores, and threads.  An example  of the new output is
 	  &quot;FreeBSD/SMP: 1 package(s) x 2 groups x 2 cache groups
 	  x 4 core(s) x 2 hardware threads&quot;.</li>
 
 	<li>The amdsmn(4) driver for accessing SMN (System Management
 	  Network) registers was added.</li>
 
 	<li>CPU temperature monitoring support for Zen was added to
 	  amdtemp(4).</li>
 
 	<li>In cpufreq(4):
 	  <ul>
 	    <li>Added support for decoding Zen P-state info from MSRs
 	      (mostly not necessary due to ACPI P-state information,
 	      but potentially useful)</li>
 
 	    <li>Work around the apparent Ryzen inability to achieve
 	      the P1 state by not busying cores waiting to
 	      transition.</li>
 	  </ul>
 	</li>
 
 	<li>The intpm(4) smbus driver was fixed to attach to FCH
 	  (Fusion Controller Hub).</li>
 
 	<li>All MCA banks are now enabled and monitored on Zen
 	  CPUs.</li>
 
 	<li>Feature bit decoding was added for: CLZERO, SVM features,
 	  RAS capabilities.</li>
 
 	<li>SHA intrinsic support was added to the aesni(4) driver.
 	  Ryzen is currently the only desktop processor to feature
 	  these intrinsics.  Support is also present in Intel's
 	  Goldmont line of low end SoCs.</li>
       </ul>
 
       <p>Overall, Zen is now a very usable platform for x86
 	workstations and servers.</p>
     </body>
 
     <sponsor>Dell EMC Isilon</sponsor>
 
     <help>
       <task>Add HWPMC support for new performance counters in
 	Zen.</task>
 
       <task>Add support for the CCP (Crypto Co-Processor).</task>
     </help>
   </project>
+
+  <project cat='bin'>
+    <title>Updates to GDB</title>
+
+    <contact>
+      <person>
+	<name>
+	  <given>John</given>
+	  <common>Baldwin</common>
+	</name>
+	<email>jhb@FreeBSD.org</email>
+      </person>
+
+      <person>
+	<name>
+	  <given>Luca</given>
+	  <common>Pizzamiglio</common>
+	</name>
+	<email>pizzamig@FreeBSD.org</email>
+      </person>
+    </contact>
+
+    <body>
+      <p>The port has been updated to GDB 8.0.</p>
+
+      <p>Support for &os;/aarch64 userland binaries has been committed
+	upstream.  These patches, along with support for debugging
+	&os;/aarch64 kernels, have been committed to the port.</p>
+
+      <p>Upstream patches adding improved support for &os;/arm userland
+	binaries are currently in review.  &os; 12 has recently grown
+	support for debugging VFP registers via <tt>ptrace()</tt> and
+	core dumps as part of this work.  Support for &os;/arm kernels
+	will be added to the port after the upstream patches are added
+	to the port.</p>
+
+       <p>Support for <tt>$_siginfo</tt> has been committed upstream.
+	 This uses the recently added NT_LWPINFO note to extract
+	 signal information from process cores.</p>
+
+       <p>Hangs that occured when GDB's <tt>kill</tt> command was used
+	 were fixed in &os; in r313992.</p>
+    </body>
+
+    <help>
+      <task>Figure out why the powerpc <tt>kgdb</tt> targets are not able to
+	unwind the stack past the initial frame.</task>
+
+      <task>Test support for sparc64 binaries and kernels.</task>
+
+      <task>Add support for debugging powerpc vector registers.</task>
+
+      <task>Implement <tt>info proc</tt> commands.</task>
+
+      <task>Implement <tt>info os</tt> commands.</task>
+    </help>
+  </project>
 </report>