public inbox for gcc-cvs-wwwdocs@sourceware.org help / color / mirror / Atom feed
From: Gerald Pfeifer <gerald@sourceware.org> To: gcc-cvs-wwwdocs@gcc.gnu.org Subject: gcc-wwwdocs branch master updated. 935fcdebfb2fb4dcd89edb51ebed5f1be0fb41e5 Date: Thu, 2 Mar 2023 22:59:15 +0000 (GMT) [thread overview] Message-ID: <20230302225915.8804C3858428@sourceware.org> (raw) This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "gcc-wwwdocs". The branch, master has been updated via 935fcdebfb2fb4dcd89edb51ebed5f1be0fb41e5 (commit) from 7c5925997a1a6fef98e29c7a4ed946924ec23df8 (commit) Those revisions listed above that are new to this repository have not appeared on any other notification email; so we list those revisions in full, below. - Log ----------------------------------------------------------------- commit 935fcdebfb2fb4dcd89edb51ebed5f1be0fb41e5 Author: Gerald Pfeifer <gerald@pfeifer.com> Date: Thu Mar 2 23:58:29 2023 +0100 gcc-13: Use < and > 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 <stdlib.h> 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> ----------------------------------------------------------------------- Summary of changes: htdocs/gcc-13/porting_to.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) hooks/post-receive -- gcc-wwwdocs
reply other threads:[~2023-03-02 22:59 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20230302225915.8804C3858428@sourceware.org \ --to=gerald@sourceware.org \ --cc=gcc-cvs-wwwdocs@gcc.gnu.org \ /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: linkBe 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).