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:27:00 -0000	[thread overview]
Message-ID: <20090729072714.28601.qmail@sourceware.org> (raw)
In-Reply-To: <bug-40898-13404@http.gcc.gnu.org/bugzilla/>



------- Comment #2 from burnus at gcc dot gnu dot org  2009-07-29 07:27 -------
>From the thread at c.l.f:

"A little testing revealed that the assembly code is correct, only the mangled 
 name is wrong when there is a character argument.  Perhaps the mangled name
 takes into account a spurious hidden LEN parameter while the code
 generator knows there is no such thing."


The issue is: While I corrected the procedure call and the creation of the
procedure itself for BIND(C) [i.e. no hidden-length argument; probably also
returning a "char" instead of a "char, char_len" as return argument], I forgot
to update the declaration of external functions, namely: gfc_get_function_type

That should also help with -fwhole-file issues.


-- 

burnus at gcc dot gnu dot org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         AssignedTo|unassigned at gcc dot gnu   |burnus at gcc dot gnu dot
                   |dot org                     |org
             Status|UNCONFIRMED                 |ASSIGNED
     Ever Confirmed|0                           |1
   Last reconfirmed|0000-00-00 00:00:00         |2009-07-29 07:27:13
               date|                            |


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


  parent reply	other threads:[~2009-07-29  7:27 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 ` [Bug fortran/40898] " burnus at gcc dot gnu dot org
2009-07-29  7:27 ` burnus at gcc dot gnu dot org [this message]
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=20090729072714.28601.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).