public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "burnus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/54262] New: LOC shouldn't use copy-in/copy-out Date: Tue, 14 Aug 2012 20:49:00 -0000 [thread overview] Message-ID: <bug-54262-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54262 Bug #: 54262 Summary: LOC shouldn't use copy-in/copy-out Classification: Unclassified Product: gcc Version: 4.8.0 Status: UNCONFIRMED Keywords: wrong-code Severity: normal Priority: P3 Component: fortran AssignedTo: unassigned@gcc.gnu.org ReportedBy: burnus@gcc.gnu.org With CONTIGUOUS, the following program assigns the address of x->data to the C pointer. However, without CONTIGUOUS one gets a copy-in/copy-out. Expected: Also without CONTIGUOUS, one obtains the x->data address – and no array is packed. The expected result is in line with F2008/TS29113's handling of C_LOC. Implementation: It might be possible to generate an interface for LOC where the dummy is of "type(*), dimension(..)" – that could be sufficient, but for scalars it requires a wrapper. Test case: subroutine foo(x, p) use iso_c_binding type(*), target, CONTIGUOUS :: x(..) ! or x(:) type(c_ptr) :: p p = transfer (loc(x), p) end subroutine foo
next reply other threads:[~2012-08-14 20:49 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-08-14 20:49 burnus at gcc dot gnu.org [this message] 2012-08-15 8:12 ` [Bug fortran/54262] " burnus at gcc dot gnu.org
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=bug-54262-4@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@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).