This has been redundant for 8+ years, and in the course of simplifying
things globally I noticed and yanked this now.

Gerald

Index: projects/tree-ssa/tree-browser.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/projects/tree-ssa/tree-browser.html,v
retrieving revision 1.2
diff -u -r1.2 tree-browser.html
--- projects/tree-ssa/tree-browser.html 30 Nov 2002 15:44:50 -0000      1.2
+++ projects/tree-ssa/tree-browser.html 8 May 2011 12:47:53 -0000
@@ -8,7 +8,7 @@
     
     Until recently the only way to debug trees from gdb was to call debug_tree 
as follows:
     
-    <table border="1" width="100%" bgcolor="#ffffff">
+    <table border="1" width="100%">
       <tr> 
        <td>
          <pre>
@@ -21,7 +21,7 @@
     An alternative for interactively scan tree structures is to use the Tree 
Browser.
     You can access Tree Browser from anywhere during a debugging session as 
follows:
 
-    <table border="1" width="100%" bgcolor="#ffffff">
+    <table border="1" width="100%">
       <tr> 
        <td>
          <pre>
@@ -37,7 +37,7 @@
     </table>
 
 For listing available commands, you could try:
-    <table border="1" width="100%" bgcolor="#ffffff">
+    <table border="1" width="100%">
       <tr> 
        <td>
          <pre>
@@ -109,7 +109,7 @@
     
     Now let's try some of these commands: we're on the declaration of the 
current function, 
     we can have a look at its body.
-    <table border="1" width="100%" bgcolor="#ffffff">
+    <table border="1" width="100%">
       <tr> 
        <td>
          <pre>
@@ -140,7 +140,7 @@
     The above output is a pretty-print of the body of the current function.
     A call to debug_tree would have printed more things about the structure of
     the Abstract Syntax Trees (AST), as follows:    
-    <table border="1" width="100%" bgcolor="#ffffff">
+    <table border="1" width="100%">
       <tr> 
        <td>
          <pre>
@@ -207,7 +207,7 @@
     and a block.  All these fields are accessible from Tree Browser.  <br/>
 
     Thus if we continue our exploration of the current tree structure, 
-    <table border="1" width="100%" bgcolor="#ffffff">
+    <table border="1" width="100%">
       <tr> 
        <td>
          <pre>
@@ -250,7 +250,7 @@
     information about the position of this expression in the original source 
code. <br/>
     
     For accessing the next expression you can use the next command: 
-    <table border="1" width="100%" bgcolor="#ffffff">
+    <table border="1" width="100%">
       <tr> 
        <td>
          <pre>
@@ -289,7 +289,7 @@
 
     You can choose to go backwards via the history stack: this pops the last 
visited
     node from the stack.
-    <table border="1" width="100%" bgcolor="#ffffff">
+    <table border="1" width="100%">
       <tr> 
        <td>
          <pre>
@@ -310,7 +310,7 @@
 
     Or via the previous expression command (this information is not yet 
included in GCC's trees,
     Tree Browser stores it in a hash table):
-    <table border="1" width="100%" bgcolor="#ffffff">
+    <table border="1" width="100%">
       <tr> 
        <td>
          <pre>

Reply via email to