Re: xemacs coredump in M-x eval-print-last-sexp
Jeff Mincy <jeff(a)delphioutpost.com> wrote:
On 16 Jul 2002, james(a)eecs.ku.edu wrote:
> Adrian Aichner <adrian(a)xemacs.org> wrote:
>> Compiler optimization bugs spring to mind.
>>
>> Are you compiling with optimization?
>>
>> What's your
>> M-x describe-installation?
Yes, it is beginning to look like some sort of compiler issue.
It is definitely a compiler bug. With gcc 2.95.3, using
"-mcpu=ultrasparc -O2" triggers the segfault. Using "-mcpu=ultrasparc
-O" gives the correct behavior. I tried for awhile to track down which
specific optimization is triggering the problem, but didn't find it.
Somebody who cares enough to figure it out but has more patience than me
doesn't need to bother trying any of these: -fno-force-mem,
-fno-force-addr, -fno-strength-reduce, -fno-delayed-branch,
-fno-schedule-insns, -fno-schedule-insns2.
Regards,
--
Jerry James
http://www.ittc.ku.edu/~james/