From: "Eli Zaretskii" <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Problem with library images on Windows (again)
Date: Thu, 19 May 2005 22:05:27 +0300 [thread overview]
Message-ID: <01c55ca5$Blat.v2.4$dd149500@zahav.net.il> (raw)
In-Reply-To: <f7ccd24b05051901133887ee61@mail.gmail.com> (message from Juanma Barranquero on Thu, 19 May 2005 10:13:23 +0200)
> Date: Thu, 19 May 2005 10:13:23 +0200
> From: Juanma Barranquero <lekktu@gmail.com>
>
> tiff_load pushes EBX into the stack, and then goes around happily
> pushing arguments and calling functions from the TIFF library, which
> apparently don't remove their arguments from the stack (nor does it
> the tiff_load code). So the stack keeps growing
This sounds incredible. MSVC generally produces good code, so I find
it hard to believe that it violates the C ABI, whereby the caller
should pop arguments off the stack. Are you sure this is indeed what
happens? Can you show some evidence, like disassembly of code around
the call to tiff_load, which would show how arguments are pushed onto
the stack and never popped off it?
next prev parent reply other threads:[~2005-05-19 19:05 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-18 15:53 Problem with library images on Windows (again) Juanma Barranquero
2005-05-18 19:30 ` Andreas Schwab
2005-05-18 22:44 ` Juanma Barranquero
2005-05-19 6:58 ` Jason Rumney
2005-05-18 22:16 ` Jason Rumney
2005-05-18 22:52 ` Juanma Barranquero
2005-05-19 3:50 ` Eli Zaretskii
2005-05-19 8:13 ` Juanma Barranquero
2005-05-19 19:05 ` Eli Zaretskii [this message]
2005-05-19 19:31 ` Juanma Barranquero
2005-05-19 19:32 ` Juanma Barranquero
2005-05-20 7:20 ` Eli Zaretskii
2005-05-20 8:24 ` Kim F. Storm
2005-05-20 10:01 ` Eli Zaretskii
2005-05-20 10:16 ` Jason Rumney
2005-05-20 10:42 ` Juanma Barranquero
2005-05-20 14:44 ` Eli Zaretskii
2005-05-20 15:46 ` Jason Rumney
2005-05-20 15:52 ` Eli Zaretskii
2005-05-20 16:33 ` Juanma Barranquero
2005-05-20 17:57 ` Juanma Barranquero
2005-05-21 10:21 ` Jason Rumney
2005-05-21 10:33 ` Juanma Barranquero
2005-05-21 21:13 ` Jason Rumney
2005-05-22 21:21 ` Juanma Barranquero
2005-06-03 12:08 ` Juanma Barranquero
2005-06-03 13:06 ` David Kastrup
2005-06-03 15:28 ` jasonr
2005-06-03 17:23 ` Stefan Monnier
2005-06-05 0:44 ` Juanma Barranquero
2005-06-06 11:26 ` Juanma Barranquero
2005-06-14 2:02 ` Juanma Barranquero
2005-06-14 7:32 ` David Kastrup
2005-06-14 9:15 ` Juanma Barranquero
2005-05-20 16:31 ` Juanma Barranquero
2005-05-20 16:29 ` Juanma Barranquero
2005-05-20 12:19 ` Benjamin Riefenstahl
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='01c55ca5$Blat.v2.4$dd149500@zahav.net.il' \
--to=eliz@gnu.org \
--cc=emacs-devel@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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).