From: David Koppelman <koppel@ece.lsu.edu>
Subject: Error with -O3 but not -O2: "Wrong type argument: listp".
Date: Sat, 28 Jan 2006 15:17:14 -0600 [thread overview]
Message-ID: <7wy810kq79.fsf@ece.lsu.edu> (raw)
I've encountered errors in temacs, the same one described by Clemens
Schueller, when make bootstrap is run with "-O3" optimization; -O0,
-O1, and -O2 work fine. The errors vary with build options but they
all start with "Wrong type argument: listp":
Wrong type argument: listp, -134393892
Wrong type argument: listp, 0
Wrong type argument: listp, [-134218836 [-134218836 #0 gmake[2]: *** [bootstrap-emacs] Segmentation fault
Wrong type argument: listp, []
The lisp error that's followed by a segmentation fault occurs when
loadup.el is loading font-lock. Others occur elsewhere.
The error occurs on today's repository code. I also tried pulling
earlier versions, including 6 January, and the problem occurs there
too.
I'm running on:
Linux nested 2.6.9-22.0.1.ELsmp #1 SMP Tue Oct 18 18:39:27 EDT 2005 i686 i686 i386 GNU/Linux
and compiling with
gcc version 3.4.4 20050721 (Red Hat 3.4.4-2)
Is there anything I can do to track down the problem, perhaps
some kind of sanity test?
If it's any help, the difference between -O2 and -O3:
`-O3'
Optimize yet more. `-O3' turns on all optimizations specified by
`-O2' and also turns on the `-finline-functions', `-fweb' and
`-frename-registers' options.
I can try compiling at -O2 and try out one of the -O3 optimizations at
a time, if that would help.
next reply other threads:[~2006-01-28 21:17 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-28 21:17 David Koppelman [this message]
2006-01-29 4:50 ` Error with -O3 but not -O2: "Wrong type argument: listp" Eli Zaretskii
2006-01-29 11:47 ` Romain Francoise
2006-01-29 19:25 ` Xavier Maillard
2006-01-29 12:46 ` Andreas Schwab
2006-01-29 18:12 ` David Koppelman
2006-01-30 18:46 ` Richard M. Stallman
2006-01-30 0:57 ` Richard M. Stallman
2006-01-30 15:58 ` David Koppelman
2006-01-30 19:21 ` Eli Zaretskii
2006-01-30 23:25 ` Richard M. Stallman
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=7wy810kq79.fsf@ece.lsu.edu \
--to=koppel@ece.lsu.edu \
/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).