public inbox for gcc-cvs-wwwdocs@sourceware.org help / color / mirror / Atom feed
From: abensonca@gcc.gnu.org To: gcc-cvs-wwwdocs@gcc.gnu.org Subject: gcc-wwwdocs branch master updated. b88b1edba71bbca44429c28b7518d76678ab6acb Date: Wed, 29 Jan 2020 16:35:00 -0000 [thread overview] Message-ID: <20200129163544.83356.qmail@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 b88b1edba71bbca44429c28b7518d76678ab6acb (commit) from a4646738299135fc74b4de75b2b38dbca2863195 (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 b88b1edba71bbca44429c28b7518d76678ab6acb Author: Andrew Benson <abenson@carnegiescience.edu> Date: Wed Jan 29 16:35:11 2020 +0000 Add note on ABI change due to Frotran PR93461. diff --git a/htdocs/gcc-10/changes.html b/htdocs/gcc-10/changes.html index dcce6b8..5a959a1 100644 --- a/htdocs/gcc-10/changes.html +++ b/htdocs/gcc-10/changes.html @@ -446,6 +446,13 @@ a work-in-progress.</p> objects with allocatable components. In this case, the optional arguments <code>STAT=</code> and <code>ERRMSG=</code> are currently ignored. </li> + <li> + The handling of module and submodule names has been reworked to allow the + full 63-character length mandated by the standard. Previously symbol names + were truncated if the combined length of module, submodule, and function + name exceeded 126 characters. This change therefore breaks the ABI, but only + for cases where this 126 character limit was exceeded. + </li> </ul> <!-- <h3 id="go">Go</h3> --> ----------------------------------------------------------------------- Summary of changes: htdocs/gcc-10/changes.html | 7 +++++++ 1 file changed, 7 insertions(+) hooks/post-receive -- gcc-wwwdocs
reply other threads:[~2020-01-29 16:35 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=20200129163544.83356.qmail@sourceware.org \ --to=abensonca@gcc.gnu.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).