public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Gerald Pfeifer <gerald@pfeifer.com>
To: Jakub Jelinek <jakub@redhat.com>
Cc: "Martin Liška" <mliska@suse.cz>, gcc-patches@gcc.gnu.org
Subject: Re: [wwwdocs] gcc-13/porting_to.html: Document C++ -fexcess-precision=standard
Date: Fri, 3 Mar 2023 00:05:09 +0100 (CET)	[thread overview]
Message-ID: <5fc24e23-5a3d-7e35-430d-9dead65b6b0c@pfeifer.com> (raw)
In-Reply-To: <ZAB7TAwFGPoJJqHT@tucnak>

On Thu, 2 Mar 2023, Jakub Jelinek wrote:
> +<pre><code>
> +#include <stdlib.h>

Oops, in HTML we need to spell "<" as "&lt;" and ">" as "&gt; - otherwise
the above would be seen as a tag by the name of stdlib.h. ;-)

I pushed the follow-up patch below.

Gerald


commit 935fcdebfb2fb4dcd89edb51ebed5f1be0fb41e5
Author: Gerald Pfeifer <gerald@pfeifer.com>
Date:   Thu Mar 2 23:58:29 2023 +0100

    gcc-13: Use &lt; and &gt; where necessary

diff --git a/htdocs/gcc-13/porting_to.html b/htdocs/gcc-13/porting_to.html
index f0ccef69..953e1453 100644
--- a/htdocs/gcc-13/porting_to.html
+++ b/htdocs/gcc-13/porting_to.html
@@ -129,7 +129,7 @@ constants and expressions.  E.g. for <code>FLT_EVAL_METHOD</code> equal
 to 2 on ia32:
 
 <pre><code>
-#include <stdlib.h>
+#include &lt;stdlib.h&gt;
 void foo (void) { if (1.1f + 3.3f != 1.1L + 3.3L) abort (); }
 void bar (void) { double d = 4.2; if (d == 4.2) abort (); }
 </code></pre>

  parent reply	other threads:[~2023-03-02 23:05 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-09 16:20 [wwwdocs] gcc-13/changes.html: " Jakub Jelinek
2023-02-10  9:06 ` Gerald Pfeifer
2023-03-02 10:32   ` [wwwdocs] gcc-13/porting_to.html: " Jakub Jelinek
2023-03-02 12:40     ` Martin Liška
2023-03-02 23:05     ` Gerald Pfeifer [this message]
2023-03-02 23:16       ` Jakub Jelinek
2023-03-09  7:09     ` Gerald Pfeifer
2023-03-09  8:05       ` Jakub Jelinek

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5fc24e23-5a3d-7e35-430d-9dead65b6b0c@pfeifer.com \
    --to=gerald@pfeifer.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=jakub@redhat.com \
    --cc=mliska@suse.cz \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).