public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "burnus at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/40898] STDCALL mangling problem for strings @8 instead of @4
Date: Wed, 29 Jul 2009 07:04:00 -0000	[thread overview]
Message-ID: <20090729070418.18476.qmail@sourceware.org> (raw)
In-Reply-To: <bug-40898-13404@http.gcc.gnu.org/bugzilla/>



------- Comment #1 from burnus at gcc dot gnu dot org  2009-07-29 07:04 -------
Function declaration

       function LoadLibrary(lpFileName) bind(C,name='LoadLibraryA')
!gcc$ ATTRIBUTES STDCALL :: LoadLibrary
         use ISO_C_BINDING

... and use

hmodule = LoadLibrary('fun.dll'//achar(0))

... and dump

hmodule = loadlibrary (&"fun.dll"[1]{lb: 1 sz: 1});

Reported error:

  undefined reference to `LoadLibraryA@8'

For a 32bit system, one expects a single 4-bye pointer and thus @4. However, I
do not see any reason why it should be 64bit instead of 32bits. It also cannot
be a 64bit Windows as one there does not use STDCALL.


-- 

burnus at gcc dot gnu dot org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |fxcoudert at gcc dot gnu dot
                   |                            |org


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=40898


  reply	other threads:[~2009-07-29  7:04 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-29  6:18 [Bug fortran/40898] New: " burnus at gcc dot gnu dot org
2009-07-29  7:04 ` burnus at gcc dot gnu dot org [this message]
2009-07-29  7:27 ` [Bug fortran/40898] " burnus at gcc dot gnu dot org
2009-07-29  7:32 ` fxcoudert at gcc dot gnu dot org
2009-07-29 10:21 ` burnus at gcc dot gnu dot org
2009-07-29 10:28 ` fxcoudert at gcc dot gnu dot org
2009-07-29 14:45 ` burnus at gcc dot gnu dot org
2009-07-29 14:47 ` burnus at gcc dot gnu dot 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=20090729070418.18476.qmail@sourceware.org \
    --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: 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).