unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Fabrice Popineau <fabrice.popineau@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 李丁 <iamliding@gmail.com>, 13939 <13939@debbugs.gnu.org>
Subject: bug#13939: 24.3; Emacs 24.3 release won't compile on Windows with the msvc toolchain
Date: Thu, 14 Mar 2013 16:13:09 +0100	[thread overview]
Message-ID: <CAFgFV9NpNhbq+A0=DP0n3NSa-rTZ8Q7RK38Z3x1h2yyRtBj9Zg@mail.gmail.com> (raw)
In-Reply-To: <83ppz3i1ni.fsf@gnu.org>

[-- Attachment #1: Type: text/plain, Size: 1001 bytes --]

> 2. GC_MARK_STACK is 1 by default in config.nt, but this default is broken
> > with the msvc toolchain.  When temacs started to dump,
> > it immediately exited with the message `Invalid function: "DEAD"'. Eli
> had
> > previously told me (in #12878) to see bug #13070, but it didn't solve the
> > problem. When I tried to change GC_MARK_STACK to 0, Emacs compiled fine.
> So
> > there must be something wrong about the GCPROS_NOOPS way of marking stack
> > under the vc compiler, maybe someone familiar with the garbage collector
> > can fix it. (MinGW gcc is ok with the default)
>
> Not only MinGW, but I believe Fabrice (CC'ed) also builds Emacs with
> MSVC and uses GC_MARK_STACK.  Fabrice, can you please comment on this?
>

I can confirm that with GC_MARK_STACK=0, 24.3 does compile with the MS
compiler.
With GC_MARK_STACK=1, 24.3 doesn't compile, but the current trunk (well, my
copy, but which is quite close) does compile, 32bits and 64bits.
It may be a bit hairy to find out why.

Fabrice

[-- Attachment #2: Type: text/html, Size: 1597 bytes --]

  reply	other threads:[~2013-03-14 15:13 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-12 22:47 bug#13939: 24.3; Emacs 24.3 release won't compile on Windows with the msvc toolchain 李丁
2013-03-13 18:40 ` Eli Zaretskii
2013-03-14 15:13   ` Fabrice Popineau [this message]
2013-03-14 18:06     ` Eli Zaretskii
2013-03-14 19:28       ` Fabrice Popineau
2013-03-14 20:02         ` Eli Zaretskii
2013-03-14 21:06           ` Fabrice Popineau
2013-03-15  7:20             ` Eli Zaretskii
2013-03-14  1:21 ` 李丁
2013-03-14  7:45   ` Fabrice Popineau
2013-03-15  5:45 ` 李丁
2013-03-15  9:39   ` Fabrice Popineau
2013-03-15 15:07     ` 李丁
2013-03-15 15:24       ` Fabrice Popineau
2013-03-15 15:43         ` Eli Zaretskii
2013-03-15 19:49         ` Fabrice Popineau
2013-03-15 20:02           ` Eli Zaretskii
2013-03-15 15:34       ` Eli Zaretskii
2013-03-16  6:12         ` 李丁
2013-03-16  8:57           ` Eli Zaretskii
2013-03-16 15:31             ` 李丁
2013-03-16 15:58               ` Eli Zaretskii
2013-03-17  2:58                 ` 李丁
2013-03-17  8:43                   ` Fabrice Popineau
2013-03-17 18:36                     ` 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='CAFgFV9NpNhbq+A0=DP0n3NSa-rTZ8Q7RK38Z3x1h2yyRtBj9Zg@mail.gmail.com' \
    --to=fabrice.popineau@gmail.com \
    --cc=13939@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=iamliding@gmail.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.
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).