unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Juanma Barranquero <lekktu@gmail.com>
Cc: Emacs developers <emacs-devel@gnu.org>
Subject: Re: [Emacs-diffs] /srv/bzr/emacs/trunk r112828: Merge the specpdl and backtrace stacks. Make the structure of the
Date: Mon, 03 Jun 2013 14:25:47 -0400	[thread overview]
Message-ID: <jwvbo7nyrzq.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <CAAeL0SRo2q6gyj_TZ0e8xB+NYho-hcindfQFKEe=fi0-hxOehw@mail.gmail.com> (Juanma Barranquero's message of "Mon, 3 Jun 2013 15:59:18 +0200")

> On Windows:

> eval.o: In function `Fsignal':
> c:\Devel\emacs\repo\debug\src/eval.c:1409: undefined reference to
> `backtrace_top'

Hmm... for some other reasons I just installed a patch that turns the
LISP_INLINE into EXTERN_INLINE.  With some luck, it may fix this
problem, but if it doesn't, we'll have to ask Paul, because I really
don't have enough of clue about what is the detailed semantics of those
INLINE annotations.

This said, I'm really surprised to see such problems, since
backtrace_(top|p|next) are defined in eval.c, before any use, so if code
from eval.c after the definition can't use those functions, it begs the
question: where can such <foo>INLINE functions be used?


        Stefan



  parent reply	other threads:[~2013-06-03 18:25 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <E1UjQtA-0006p7-My@vcs.savannah.gnu.org>
2013-06-03 13:59 ` [Emacs-diffs] /srv/bzr/emacs/trunk r112828: Merge the specpdl and backtrace stacks. Make the structure of the Juanma Barranquero
2013-06-03 14:01   ` Juanma Barranquero
2013-06-03 18:25   ` Stefan Monnier [this message]
2013-06-03 19:23     ` Eli Zaretskii
2013-06-04  5:55       ` Paul Eggert
2013-06-04 15:13         ` Eli Zaretskii
2013-06-18 18:50           ` Paul Eggert
2013-06-18 19:05             ` Eli Zaretskii
2013-06-18 20:56               ` Paul Eggert

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=jwvbo7nyrzq.fsf-monnier+emacs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=emacs-devel@gnu.org \
    --cc=lekktu@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).