From: Andrew Benson <abenson@carnegiescience.edu>
To: Tobias Burnus <tobias@codesourcery.com>
Cc: fortran@gcc.gnu.org, gcc-patches@gcc.gnu.org, gerald@pfeifer.com
Subject: Re: [patch, fortran, wwwdocs] PR93461 - Bogus "symbol is already defined" with long subroutine names in submodule
Date: Wed, 29 Jan 2020 00:45:00 -0000 [thread overview]
Message-ID: <1693806.094PflFsSv@andrew-precision-3520> (raw)
In-Reply-To: <facca8b9-6cd1-9a09-5638-90ad532f1429@codesourcery.com>
[-- Attachment #1: Type: text/plain, Size: 746 bytes --]
Hi Tobias,
On Tuesday, January 28, 2020 6:49:54 PM PST Tobias Burnus wrote:
> Thus, I do not think it is a real problem in practice. We could be nice,
> however, and add a note to the release notes (i.e.
> https://gcc.gnu.org/gcc-10/changes.html); I not completely sure whether
> it is worthwhile but why not. [See https://gcc.gnu.org/about.html#git
> about how to change WWW files and CC Gerald as web maintainer when
> submitting wwwdocs patches.]
I've attached a draft patch to update the release notes about this ABI
breakage. I don't know if I've explained it sufficiently clearly though?
-Andrew
--
* Andrew Benson: http://users.obs.carnegiescience.edu/abenson/contact.html
* Galacticus: https://github.com/galacticusorg/galacticus
[-- Attachment #2: patch.diff --]
[-- Type: text/x-patch, Size: 805 bytes --]
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> -->
next prev parent reply other threads:[~2020-01-29 0:45 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-25 20:51 ICE in gfc_new_symbol() due to overlong symbol name Andrew Benson
2018-09-04 16:43 ` [patch, fortan] PR87103 - [OOP] " Andrew Benson
2018-09-04 17:43 ` Bernhard Reutner-Fischer
[not found] ` <5aa0135b-1bdd-46de-e235-daed0a9a97e1@charter.net>
2018-09-05 10:35 ` Bernhard Reutner-Fischer
2018-09-05 14:24 ` Andrew Benson
2019-08-24 21:15 ` Andrew Benson
2019-08-28 22:48 ` Bernhard Reutner-Fischer
2019-08-30 8:22 ` Andrew Benson
2020-01-29 20:19 ` Andrew Benson
2020-01-30 16:28 ` Bernhard Reutner-Fischer
2020-01-30 17:50 ` Andrew Benson
2020-01-27 20:57 ` [patch, fortran] PR93461 - Bogus "symbol is already defined" with long subroutine names in submodule Andrew Benson
2020-01-28 8:21 ` Tobias Burnus
2020-01-28 16:41 ` Andrew Benson
2020-01-28 17:50 ` Tobias Burnus
2020-01-28 18:14 ` Andrew Benson
2020-01-29 0:45 ` Andrew Benson [this message]
2020-01-29 9:08 ` [patch, fortran, wwwdocs] " Gerald Pfeifer
2020-01-29 10:57 ` Tobias Burnus
2020-01-29 16:37 ` Andrew Benson
2020-01-27 23:41 ` [patch, fortran] PR93473 - ICE on valid with long module + submodule names Andrew Benson
2020-01-28 8:28 ` Tobias Burnus
2020-01-28 16:41 ` Andrew Benson
2020-01-28 17:32 ` Tobias Burnus
2020-01-28 18:05 ` Andrew Benson
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=1693806.094PflFsSv@andrew-precision-3520 \
--to=abenson@carnegiescience.edu \
--cc=fortran@gcc.gnu.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=gerald@pfeifer.com \
--cc=tobias@codesourcery.com \
/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).