[Bug fortran/56149] 64 bit gFortran-C interop hidden character argument length passed as 32 bit value

2016-04-09 Thread dominiq at lps dot ens.fr
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=56149 Dominique d'Humieres changed: What|Removed |Added Status|WAITING |RESOLVED Resolution|---

[Bug fortran/56149] 64 bit gFortran-C interop hidden character argument length passed as 32 bit value

2015-10-09 Thread dominiq at lps dot ens.fr
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=56149 Dominique d'Humieres changed: What|Removed |Added Status|UNCONFIRMED |WAITING Last reconfirmed|

[Bug fortran/56149] 64 bit gFortran-C interop hidden character argument length passed as 32 bit value

2013-11-24 Thread kargl at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56149 kargl at gcc dot gnu.org changed: What|Removed |Added CC|kargl at gcc dot gnu.org | --- Comment #8 from kar

[Bug fortran/56149] 64 bit gFortran-C interop hidden character argument length passed as 32 bit value

2013-01-31 Thread sgk at troutmask dot apl.washington.edu
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56149 --- Comment #7 from Steve Kargl 2013-02-01 05:21:58 UTC --- On Thu, Jan 31, 2013 at 04:29:46PM +, paul.laidler at ntlworld dot com wrote: > --- Comment #6 from Paul Laidler > 2013-01-31 16:29:46 UTC --- > Yes, winio is written in C

[Bug fortran/56149] 64 bit gFortran-C interop hidden character argument length passed as 32 bit value

2013-01-31 Thread paul.laidler at ntlworld dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56149 --- Comment #6 from Paul Laidler 2013-01-31 16:29:46 UTC --- Yes, winio is written in C with the binding "int winio(char *string, ...)" and it is not Fortran standard conforming. In my opinion there should be no problem with backwards co

[Bug fortran/56149] 64 bit gFortran-C interop hidden character argument length passed as 32 bit value

2013-01-31 Thread sgk at troutmask dot apl.washington.edu
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56149 --- Comment #5 from Steve Kargl 2013-01-31 15:54:56 UTC --- On Wed, Jan 30, 2013 at 07:58:27PM +, paul.laidler at ntlworld dot com wrote: > --- Comment #2 from Paul Laidler > 2013-01-30 19:58:27 UTC --- > > Many thanks for your re

[Bug fortran/56149] 64 bit gFortran-C interop hidden character argument length passed as 32 bit value

2013-01-31 Thread paul.laidler at ntlworld dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56149 --- Comment #4 from Paul Laidler 2013-01-31 08:31:48 UTC --- Many thanks for your helpful comments. I take the point, though backwards compatibility can often be maintained by allowing the size of the relevant integers to vary with the (32

[Bug fortran/56149] 64 bit gFortran-C interop hidden character argument length passed as 32 bit value

2013-01-30 Thread burnus at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56149 Tobias Burnus changed: What|Removed |Added CC||burnus at gcc dot gnu.org --- C

[Bug fortran/56149] 64 bit gFortran-C interop hidden character argument length passed as 32 bit value

2013-01-30 Thread paul.laidler at ntlworld dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56149 --- Comment #2 from Paul Laidler 2013-01-30 19:58:27 UTC --- Hi Many thanks for your reply and interest. The ClearWin+ function winio@ (winio$ in gFortran) emulates the C function printf that takes a format string then a variable numb

[Bug fortran/56149] 64 bit gFortran-C interop hidden character argument length passed as 32 bit value

2013-01-30 Thread kargl at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56149 kargl at gcc dot gnu.org changed: What|Removed |Added Priority|P3 |P5 CC|