public inbox for gcc-cvs-wwwdocs@sourceware.org help / color / mirror / Atom feed
From: Jonathan Wakely <redi@sourceware.org> To: gcc-cvs-wwwdocs@gcc.gnu.org Subject: gcc-wwwdocs branch master updated. f83141b2c816b09a2dd44ea5a84d868b7f0e50e7 Date: Mon, 30 Oct 2023 15:09:36 +0000 (GMT) [thread overview] Message-ID: <20231030150937.00E193857722@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 f83141b2c816b09a2dd44ea5a84d868b7f0e50e7 (commit) from 9892454a3d0fc4a741719701f749b8c1e4d47939 (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 f83141b2c816b09a2dd44ea5a84d868b7f0e50e7 Author: Jonathan Wakely <jwakely@redhat.com> Date: Mon Oct 30 14:43:17 2023 +0000 Add "Porting to GCC 14" diff --git a/htdocs/gcc-14/porting_to.html b/htdocs/gcc-14/porting_to.html new file mode 100644 index 00000000..dea9ac80 --- /dev/null +++ b/htdocs/gcc-14/porting_to.html @@ -0,0 +1,50 @@ +<!DOCTYPE html> +<html lang="en"> + +<head> +<meta http-equiv="Content-Type" content="text/html; charset=utf-8"> +<title>Porting to GCC 14</title> +<link rel="stylesheet" type="text/css" href="https://gcc.gnu.org/gcc.css"> +</head> + +<body> +<h1>Porting to GCC 14</h1> + +<p> +The GCC 14 release series differs from previous GCC releases in +<a href="changes.html">a number of ways</a>. Some of these are a result +of bug fixing, and some old behaviors have been intentionally changed +to support new standards, or relaxed in standards-conforming ways to +facilitate compilation or run-time performance. +</p> + +<p> +Some of these changes are user visible and can cause grief when +porting to GCC 14. This document is an effort to identify common issues +and provide solutions. Let us know if you have suggestions for improvements! +</p> + +<h2 id="cxx">C++ language issues</h2> + +<h3 id="header-dep-changes">Header dependency changes</h3> +<p>Some C++ Standard Library headers have been changed to no longer include +other headers that were being used internally by the library. +As such, C++ programs that used standard library components without +including the right headers will no longer compile. +</p> +<p> +The following headers are used less widely in libstdc++ and may need to +be included explicitly when compiling with GCC 14: +</p> +<ul> +<li> <code><algorithm></code> + (for <code>std::copy_n</code>, <code>std::lower_bound</code>, + <code>std::remove</code>, <code>std::reverse</code>, + <code>std::sort</code> etc.) +</li> +</ul> + +<!-- <h2 id="fortran">Fortran language issues</h2> --> + +</body> +</html> ----------------------------------------------------------------------- Summary of changes: htdocs/gcc-14/porting_to.html | 50 +++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 50 insertions(+) create mode 100644 htdocs/gcc-14/porting_to.html hooks/post-receive -- gcc-wwwdocs
reply other threads:[~2023-10-30 15:09 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=20231030150937.00E193857722@sourceware.org \ --to=redi@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).