GNU bug report logs -
#20427
bug in optimizing compiler?
Previous Next
Full log
View this message in rfc822 format
[Message part 1 (text/plain, inline)]
Your message dated Mon, 27 Apr 2015 00:04:05 -0400
with message-id <jwvlhheqkus.fsf-monnier+emacsbugs <at> gnu.org>
and subject line Re: bug#20427: bug in optimizing compiler?
has caused the debbugs.gnu.org bug report #20427,
regarding bug in optimizing compiler?
to be marked as done.
(If you believe you have received this mail in error, please contact
help-debbugs <at> gnu.org.)
--
20427: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=20427
GNU Bug Tracking System
Contact help-debbugs <at> gnu.org with problems
[Message part 2 (message/rfc822, inline)]
The following report refers to this version of emacs:
GNU Emacs 24.3.1 (x86_64-pc-linux-gnu, GTK+ Version 3.10.7) of
2014-03-07 on lamiak, modified by Debian
Hello,
When I byte-compile a file containing the following code, with
optimization safety=0, the compiler deletes the assertion test.
(defmacro buggy ()
(assert nil nil "assertion failed -- it always should fail")
"This should never show up!")
This only seems to happen when i compile a file containing the
macro, not when i compile the macro individually.
Here is a full example
(the defmacro of `buggy' is in the file "bug.test.el")
(declaim (optimize (safety 3)))
(byte-compile-file "bug.test.el" 'load) ; t
(buggy) ; error: "assertion failed -- it always should fail"
(declaim (optimize (safety 0)))
(byte-compile-file "bug.test.el" 'load) ; t
(buggy) ; This should never show up!
I'm not sure whether this officially qualifies as a bug, but
it's certainly not the behavior I was expecting. (It also
doesn't seem to be present in Emacs 23.1.1)
Thanks,
Rafael
~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-
Rafael Sorkin
Perimeter Institute for Theoretical Physics
31 Caroline Street North
Waterloo, ON N2L 2Y5
Canada
~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-
[Message part 3 (message/rfc822, inline)]
tags 20427 notabug
thanks
> When I byte-compile a file containing the following code, with
> optimization safety=0, the compiler deletes the assertion test.
That's expected. Just like C's `assert', CL's `assert' can be compiled
out depending on compilation options (in this case, depending on the
`safety' setting).
Stefan
This bug report was last modified 10 years and 84 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.