public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Sergey Okhapkin <sos@prospect.com.ru>
To: "gnu-win32@cygnus.com" <gnu-win32@cygnus.com>,
	"'Thomas Nichols'" <thomas.nichols@iname.com>
Subject: RE: MFC with egcs 1.1 (Was: MFC with CygWin)
Date: Fri, 09 Oct 1998 06:48:00 -0000	[thread overview]
Message-ID: <01BDF3A1.5EBEF8E0@sos> (raw)

Thomas Nichols wrote:
> what is the status of attempts to access the MFC DLLs from egcs? If the
> name-mangling schemes are incompatible, will this remain true in
> perpetuity, or are there plans to allow MS-style name mangling as an option
> to gcc?
> 

Name mangling is not the only problem. Gcc passes "this" pointer when calling class member on top of stack, but MSVC in ecx.

-- 
Sergey Okhapkin, http://www.lexa.ru/sos
Moscow, Russia


-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".

             reply	other threads:[~1998-10-09  6:48 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-10-09  6:48 Sergey Okhapkin [this message]
1998-10-09 11:14 ` Thomas Nichols
1998-10-10 10:34   ` Mumit Khan
1998-10-10 12:02     ` Thomas Nichols
1998-10-11 16:08       ` Precompiled headers in egcs? (was MFC with egcs 1.1) Hilton Fernandes
1998-10-11 18:22         ` Mumit Khan
1998-10-12  1:26         ` Thomas Nichols
1998-10-13  5:05         ` Don Sharp
1998-10-14  4:27           ` Hilton Fernandes
  -- strict thread matches above, loose matches on Subject: below --
1998-10-08 15:29 MFC with egcs 1.1 (Was: MFC with CygWin) Thomas Nichols
1998-10-09 11:14 ` Larry Hall

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=01BDF3A1.5EBEF8E0@sos \
    --to=sos@prospect.com.ru \
    --cc=gnu-win32@cygnus.com \
    --cc=thomas.nichols@iname.com \
    /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).