From: Eli Zaretskii <eliz@gnu.org>
To: oscarfv@telefonica.net
Cc: 18699@debbugs.gnu.org
Subject: bug#18699: 25.0.50; Windows 7: Odd length text property list
Date: Mon, 13 Oct 2014 09:14:07 +0300 [thread overview]
Message-ID: <83wq847az4.fsf@gnu.org> (raw)
In-Reply-To: <8338as8ri7.fsf@gnu.org>
> Date: Mon, 13 Oct 2014 08:31:44 +0300
> From: Eli Zaretskii <eliz@gnu.org>
> Cc: 18699@debbugs.gnu.org
>
> The function add_font_entity_to_list is decorated with a GCC attribute
> that should cause GCC to emit a few instructions in the function's
> prologue to ensure the stack is 8-byte aligned. Do you see that in the
> disassembly of that function? If not, can you show the preprocessed
> source of the first few line of that function, including its
> definition line?
Here's what I see in the preprocessed source on my machine:
static int __attribute__((__stdcall__)) __attribute__((force_align_arg_pointer))
add_font_entity_to_list (ENUMLOGFONTEX *logical_font,
NEWTEXTMETRICEX *physical_font,
DWORD font_type, LPARAM lParam)
{
struct font_callback_data *match_data
= (struct font_callback_data *) lParam;
Lisp_Object backend = match_data->opentype_only ? Quniscribe : Qgdi;
Lisp_Object entity;
The important part is the force_align_arg_pointer attribute.
This is set up in w32term.h, like this:
#ifdef __GNUC__
# if USE_STACK_LISP_OBJECTS && !defined _W64 && !defined __x86_64__ \
&& __GNUC__ + (__GNUC_MINOR__ > 1) >= 5
# define ALIGN_STACK __attribute__((force_align_arg_pointer))
# else
# define ALIGN_STACK
# endif /* USE_STACK_LISP_OBJECTS */
#endif
Is it possible that the MinGW64 compiler somehow trips here? E.g., is
it possible that, even in a 32-bit build, it defines _W64 or
__x86_64__? If so, what other preprocessor macros are available in
MinGW64 to distinguish between a 32-bit and a 64-bit build?
next prev parent reply other threads:[~2014-10-13 6:14 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-13 0:58 bug#18699: 25.0.50; Windows 7: Odd length text property list Óscar Fuentes
[not found] ` <handler.18699.B.141316196215131.ack@debbugs.gnu.org>
2014-10-13 2:02 ` Óscar Fuentes
2014-10-13 5:31 ` Eli Zaretskii
2014-10-13 6:14 ` Eli Zaretskii [this message]
2014-10-13 10:27 ` Óscar Fuentes
2014-10-13 11:37 ` Eli Zaretskii
2014-10-13 11:46 ` Óscar Fuentes
2014-10-13 12:49 ` Eli Zaretskii
2014-10-13 13:57 ` Óscar Fuentes
2014-10-13 19:07 ` Eli Zaretskii
2014-10-13 19:14 ` Ken Brown
2014-10-13 19:39 ` Óscar Fuentes
2014-10-13 20:25 ` Eli Zaretskii
2014-10-13 20:35 ` Óscar Fuentes
2014-10-14 6:09 ` Eli Zaretskii
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=83wq847az4.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=18699@debbugs.gnu.org \
--cc=oscarfv@telefonica.net \
/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).