[Bug fortran/56789] Handling of contiguous dummy arguments

2019-01-19 Thread tkoenig at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=56789 Thomas Koenig changed: What|Removed |Added Status|NEW |RESOLVED Resolution|---

[Bug fortran/56789] Handling of contiguous dummy arguments

2019-01-19 Thread tkoenig at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=56789 --- Comment #23 from Thomas Koenig --- Author: tkoenig Date: Sat Jan 19 20:06:41 2019 New Revision: 268096 URL: https://gcc.gnu.org/viewcvs?rev=268096=gcc=rev Log: 2018-01-19 Thomas Koenig Paul Thomas PR fortran/56789

[Bug fortran/56789] Handling of contiguous dummy arguments

2019-01-13 Thread pault at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=56789 --- Comment #22 from Paul Thomas --- (In reply to Thomas Koenig from comment #21) > Hi Paul, > > > I was mulling this over a few months ago and came to the conclusion > > that copy-in/copy-out was the only thing that made sense. > > Well, in

[Bug fortran/56789] Handling of contiguous dummy arguments

2019-01-13 Thread tkoenig at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=56789 Thomas Koenig changed: What|Removed |Added Assignee|pault at gcc dot gnu.org |tkoenig at gcc dot gnu.org ---

[Bug fortran/56789] Handling of contiguous dummy arguments

2019-01-13 Thread paul.richard.thomas at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=56789 --- Comment #20 from paul.richard.thomas at gmail dot com --- Hi Thomas, I was mulling this over a few months ago and came to the conclusion that copy-in/copy-out was the only thing that made sense. The IBM manual is explicit about this:

[Bug fortran/56789] Handling of contiguous dummy arguments

2019-01-13 Thread tkoenig at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=56789 --- Comment #19 from Thomas Koenig --- I have asked in https://groups.google.com/forum/#!search/comp.lang.fortran$20contiguous$20dummy%7Csort:date/comp.lang.fortran/QiFkx8b48uw/wtQE9M_aFwAJ . Let's see what sort of answers there will be, apart

[Bug fortran/56789] Handling of contiguous dummy arguments

2018-10-04 Thread anlauf at gmx dot de
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=56789 --- Comment #18 from Harald Anlauf --- (In reply to Paul Thomas from comment #12) > (In reply to Harald Anlauf from comment #11) > > (In reply to paul.richard.tho...@gmail.com from comment #10) > > > Even if that were allowed, the standard

[Bug fortran/56789] Handling of contiguous dummy arguments

2018-10-04 Thread pault at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=56789 Paul Thomas changed: What|Removed |Added Assignee|unassigned at gcc dot gnu.org |pault at gcc dot gnu.org ---

[Bug fortran/56789] Handling of contiguous dummy arguments

2018-10-03 Thread paul.richard.thomas at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=56789 --- Comment #16 from paul.richard.thomas at gmail dot com --- Hi Thomas, I think that the copy in/copy out might be rather easy to arrange. Give me a couple of days. Paul On Wed, 3 Oct 2018 at 22:01, tkoenig at gcc dot gnu.org wrote: > >

[Bug fortran/56789] Handling of contiguous dummy arguments

2018-10-03 Thread tkoenig at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=56789 --- Comment #15 from Thomas Koenig --- Of course, there should be a "return false;" in there as well.

[Bug fortran/56789] Handling of contiguous dummy arguments

2018-10-03 Thread tkoenig at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=56789 --- Comment #14 from Thomas Koenig --- This would reject the obvious non-contiguous cases. Index: interface.c === --- interface.c (Revision 264540) +++ interface.c (Arbeitskopie)

[Bug fortran/56789] Handling of contiguous dummy arguments

2018-10-03 Thread tkoenig at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=56789 Thomas Koenig changed: What|Removed |Added Keywords||diagnostic Summary|Wrong