From: Paul Eggert <eggert@cs.ucla.edu>
To: Greg Minshall <minshall@acm.org>, Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: make check fails? (emacs-26.1 w/modules)
Date: Wed, 5 Sep 2018 00:54:46 -0700 [thread overview]
Message-ID: <367ca660-33f5-f4d6-c03c-146056b4ece2@cs.ucla.edu> (raw)
In-Reply-To: <12105.1536057594@minshall-apollo.minshall.org>
Greg Minshall wrote:
> admittedly pretty old, but that's apparently what ubuntu's serving up
> these days.
It depends on the Ubuntu release. My Ubuntu 18.04 machine is running gcc (Ubuntu
7.3.0-16ubuntu3). I don't observe the symptoms you're seeing, when I build on
the emacs-26 branch and use './configure --with-modules'.
> i guess it's always possible the optimizer is doing the right thing
> because of some programming error, maybe a mis-placed "const" on an
> extern, something like that.
Doesn't sound likely. The assembly code you sent looks fishy, though. You might
try running gcc -S and/r gcc -E on the affected module, with the same
compile-time flags that 'make' is using; use 'make V=1' to see them.
next prev parent reply other threads:[~2018-09-05 7:54 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-03 14:39 make check fails? (emacs-26.1 w/modules) Greg Minshall
2018-09-03 15:12 ` Greg Minshall
2018-09-03 15:13 ` Eli Zaretskii
2018-09-03 15:16 ` Greg Minshall
2018-09-03 15:18 ` Greg Minshall
2018-09-04 10:39 ` Greg Minshall
2018-09-05 7:54 ` Paul Eggert [this message]
2018-09-05 9:14 ` Greg Minshall
2018-09-05 20:26 ` Greg Minshall
2018-09-05 20:55 ` Paul Eggert
2018-09-06 8:58 ` Robert Pluim
2018-09-06 10:32 ` Greg Minshall
2018-09-12 13:41 ` Robert Pluim
2018-09-12 14:56 ` Paul Eggert
2018-09-12 16:19 ` Greg Minshall
2018-09-12 16:37 ` Robert Pluim
2018-09-12 16:27 ` Greg Minshall
2018-09-12 16:39 ` Robert Pluim
2018-09-07 9:10 ` Greg Minshall
2018-09-03 18:27 ` Paul Eggert
2018-09-03 23:46 ` Greg Minshall
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=367ca660-33f5-f4d6-c03c-146056b4ece2@cs.ucla.edu \
--to=eggert@cs.ucla.edu \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=minshall@acm.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.