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/34112] Add $!DEC ATTRIBUTE support for 32bit Windows' STDCALL Date: Tue, 16 Jun 2009 16:36:00 -0000 [thread overview] Message-ID: <20090616163546.6837.qmail@sourceware.org> (raw) In-Reply-To: <bug-34112-13404@http.gcc.gnu.org/bugzilla/> ------- Comment #11 from burnus at gcc dot gnu dot org 2009-06-16 16:35 ------- Note information I got from Kai. (He was not 100% sure for some of the items and I probably misunderstood also parts thus take with a grain of salt.) With the stdcall attribute on Win32 the @<n> suffix is automatically added; with fastcall a @ prefix is added and with cdecl a leading _ is added. And with Win64 nothing is added (well, cdecl adds a leading _ but this is about to change). An alias does not automatically add the decoration thus the decoration attribute might be useful. (Though, we don't need to support (weak) aliases initially. For aliases, one needs in C a function prototype to get it working properly. Thus one needs to check how to handle it correctly.) Procedure pointers: Here, the calling method is also crucial, i.e. one needs to be able (a) to specify it for proc pointers and (b) one needs to check it when one does a proc pointer assignment. DLLEXPORT/DLLIMPORT: Here, one also needs to handle global variables (= common, module variables). -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=34112
next prev parent reply other threads:[~2009-06-16 16:36 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2007-11-15 18:23 [Bug fortran/34112] New: " burnus at gcc dot gnu dot org 2007-11-15 19:25 ` [Bug fortran/34112] " burnus at gcc dot gnu dot org 2007-11-16 23:09 ` dannysmith at users dot sourceforge dot net 2007-11-18 21:49 ` tkoenig at gcc dot gnu dot org 2008-02-05 10:18 ` fxcoudert at gcc dot gnu dot org 2008-02-05 15:12 ` burnus at gcc dot gnu dot org 2008-03-03 14:41 ` burnus at gcc dot gnu dot org 2008-03-04 22:21 ` burnus at gcc dot gnu dot org 2008-04-04 7:49 ` burnus at gcc dot gnu dot org 2008-04-04 8:35 ` fxcoudert at gcc dot gnu dot org 2009-06-16 14:22 ` burnus at gcc dot gnu dot org 2009-06-16 16:36 ` burnus at gcc dot gnu dot org [this message] 2009-06-28 17:57 ` burnus at gcc dot gnu dot org 2009-06-28 19:51 ` 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=20090616163546.6837.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: 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).