From: Thomas Koenig <tkoenig@netcologne.de>
To: Jerry DeLisle <jvdelisle@charter.net>,
Paul Richard Thomas <paul.richard.thomas@gmail.com>
Cc: "fortran@gcc.gnu.org" <fortran@gcc.gnu.org>,
gcc-patches <gcc-patches@gcc.gnu.org>,
Damian Rouson <damian@sourceryinstitute.org>,
"Bader, Reinhold" <Reinhold.Bader@lrz.de>
Subject: Re: [Patch, fortran] PR34640 - ICE when assigning item of a derived-component to a pointer
Date: Tue, 11 Jul 2017 18:13:00 -0000 [thread overview]
Message-ID: <ed988ec2-9b15-4666-ed08-99c00d613f55@netcologne.de> (raw)
In-Reply-To: <3db0f7be-b48b-cbd5-c526-7b29c25437d3@charter.net>
Am 11.07.2017 um 16:48 schrieb Jerry DeLisle:
> Somewhere in the threads on this, there was mentioned ABI breakage/change.
That was me.
> Does it really do this?
Yes. Look at this part:
Index: libgfortran/libgfortran.h
===================================================================
*** libgfortran/libgfortran.h (revision 250082)
--- libgfortran/libgfortran.h (working copy)
*************** struct {\
*** 339,344 ****
--- 339,345 ----
type *base_addr;\
size_t offset;\
index_type dtype;\
+ index_type span;\
descriptor_dimension dim[r];\
}
> If the significant change is in the descriptor and you
> just added the span on the end of the structure, I am not convinced
this is an
> issue. (I have not studied the patch at all, I would rather not bump
library
> version)
Unless I am mistaken, we only build the required dimensions for
an array descriptor. Putting it on the end would not work
unless we changed that behavior.
But we are doing something wrong with the array descriptors anyway. See
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68649#c7 for a description.
Other comments in the same PR have some suggestions, but nothing that
works (or so I think).
So, if we do break the ABI, we could try to fix the remaining
issues with the array descriptors - not with this patch, but
before 8.1 is released. Flexible array members come to mind.
Regards
Thomas
next prev parent reply other threads:[~2017-07-11 18:13 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-24 10:48 Paul Richard Thomas
2017-06-25 10:59 ` Thomas Koenig
2017-06-25 11:43 ` Paul Richard Thomas
2017-07-01 18:17 ` Paul Richard Thomas
2017-07-04 21:04 ` Thomas Koenig
2017-07-09 18:43 ` Paul Richard Thomas
2017-07-09 21:28 ` Thomas Koenig
2017-07-11 6:16 ` Paul Richard Thomas
2017-07-11 14:24 ` Paul Richard Thomas
2017-07-11 14:48 ` Jerry DeLisle
2017-07-11 18:13 ` Thomas Koenig [this message]
2017-07-11 20:23 ` Paul Richard Thomas
2017-09-11 19:47 ` H.J. Lu
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=ed988ec2-9b15-4666-ed08-99c00d613f55@netcologne.de \
--to=tkoenig@netcologne.de \
--cc=Reinhold.Bader@lrz.de \
--cc=damian@sourceryinstitute.org \
--cc=fortran@gcc.gnu.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=jvdelisle@charter.net \
--cc=paul.richard.thomas@gmail.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).