2012-01-11  Benjamin Kosnik  <bkoz@redhat.com>

        * htdocs/gcc-4.7/porting_to.html: Fixup for validation.

Index: htdocs/gcc-4.7/porting_to.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/gcc-4.7/porting_to.html,v
retrieving revision 1.2
diff -c -r1.2 porting_to.html
*** htdocs/gcc-4.7/porting_to.html	12 Jan 2012 01:11:40 -0000	1.2
--- htdocs/gcc-4.7/porting_to.html	12 Jan 2012 02:51:05 -0000
***************
*** 45,52 ****
  </p>
  
  <pre>
! error: unrecognized command line option ‘-Wl’
! error: unrecognized command line option ‘-mflat_namespace’
  </pre>
  
  <p>
--- 45,52 ----
  </p>
  
  <pre>
! error: unrecognized command line option &lsquo;-Wl&rsquo;
! error: unrecognized command line option &lsquo;-mflat_namespace&rsquo;
  </pre>
  
  <p>
***************
*** 88,102 ****
  </p>
  
  <pre>
! error: ‘truncate’ was not declared in this scope
  </pre>
  
  <pre>
! error: ‘sleep’ was not declared in this scope
  </pre>
  
  <pre>
! error: ‘pipe’ was not declared in this scope
  </pre>
  
  <pre>
--- 88,102 ----
  </p>
  
  <pre>
! error: &lsquo;truncate&rsquo; was not declared in this scope
  </pre>
  
  <pre>
! error: &lsquo;sleep&rsquo; was not declared in this scope
  </pre>
  
  <pre>
! error: &lsquo;pipe&rsquo; was not declared in this scope
  </pre>
  
  <pre>
***************
*** 153,162 ****
  Will result in the following diagnostic:
  </p>
  <pre>
! In instantiation of ‘int t(T) [with T = int]’:
    required from here
!   error: ‘f’ was not declared in this scope, and no declarations were found by argument-dependent lookup at the point of instantiation [-fpermissive]
!   note: ‘int f(int)’ declared here, later in the translation unit
  </pre>
  
  <p>
--- 153,162 ----
  Will result in the following diagnostic:
  </p>
  <pre>
! In instantiation of &lsquo;int t(T) [with T = int]&rsquo;
    required from here
!   error: &lsquo;f&rsquo; was not declared in this scope, and no declarations were found by argument-dependent lookup at the point of instantiation [-fpermissive]
!   note: &lsquo;int f(int)&rsquo; declared here, later in the translation unit
  </pre>
  
  <p>
***************
*** 209,216 ****
  <p>
  
  <pre>
! error: redeclaration of ‘int i’
! error: ‘int i’ previously declared here
  </pre>
  
  <p>
--- 209,216 ----
  <p>
  
  <pre>
! error: redeclaration of &lsquo;int i&rsquo;
! error: &lsquo;int i&rsquo; previously declared here
  </pre>
  
  <p>
***************
*** 221,244 ****
  <h3>User-defined literals and whitespace</h3>
  
  <p>
! The C++ compiler in ISO C11 mode -std={c++11,c++0x,gnu++11,gnu++0x}
  supports user defined literals, which are incompatible with some valid
  ISO C++03 code.
  </p>
  
  <p>
! In particular, whitespace is now needed after a string literal and before something that could be a valid user defined literal. Take the valid ISO C++03 code
  </p>
  
  <pre>
! const char *p = "foobar"__TIME__;
  </pre>
  
! <p>In C++03, the <code>__TIME__</code> macro expands to some string literal and is concatenated with the other one.  In C++11 <code>__TIME__</code> isn't expanded, instead operator "" <code>__TIME__</code> is being looked up, resulting in the following diagnostic:
  </p>
  
  <pre>
!  error: unable to find string literal operator ‘operator"" __TIME__’
  </pre>
  
  <p>
--- 221,250 ----
  <h3>User-defined literals and whitespace</h3>
  
  <p>
! The C++ compiler in ISO C11 mode <code>std={c++11,c++0x,gnu++11,gnu++0x}</code>
  supports user defined literals, which are incompatible with some valid
  ISO C++03 code.
  </p>
  
  <p>
! In particular, whitespace is now needed after a string literal and
! before something that could be a valid user defined literal. Take the
! valid ISO C++03 code
  </p>
  
  <pre>
! const char *p = &ldquo;foobar&rdquo;__TIME__;
  </pre>
  
! <p>In C++03, the <code>__TIME__</code> macro expands to some string
! literal and is concatenated with the other one.  In
! C++11 <code>__TIME__</code> isn't expanded, instead operator
! "" <code>__TIME__</code> is being looked up, resulting in the
! following diagnostic:
  </p>
  
  <pre>
!  error: unable to find string literal operator &lsquo;operator&ldquo;&rdquo; __TIME__&rsquo;
  </pre>
  
  <p>
