GNU bug report logs -
#20427
bug in optimizing compiler?
Previous Next
To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 20427 in the body.
You can then email your comments to 20427 AT debbugs.gnu.org in the normal way.
Toggle the display of automated, internal messages from the tracker.
Report forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#20427
; Package
emacs
.
(Sun, 26 Apr 2015 04:17:01 GMT)
Full text and
rfc822 format available.
Acknowledgement sent
to
Rafael D Sorkin <rsorkin <at> perimeterinstitute.ca>
:
New bug report received and forwarded. Copy sent to
bug-gnu-emacs <at> gnu.org
.
(Sun, 26 Apr 2015 04:17:02 GMT)
Full text and
rfc822 format available.
Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):
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
~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-
Added tag(s) notabug.
Request was from
Stefan Monnier <monnier <at> iro.umontreal.ca>
to
control <at> debbugs.gnu.org
.
(Mon, 27 Apr 2015 04:05:03 GMT)
Full text and
rfc822 format available.
Reply sent
to
Stefan Monnier <monnier <at> iro.umontreal.ca>
:
You have taken responsibility.
(Mon, 27 Apr 2015 04:05:04 GMT)
Full text and
rfc822 format available.
Notification sent
to
Rafael D Sorkin <rsorkin <at> perimeterinstitute.ca>
:
bug acknowledged by developer.
(Mon, 27 Apr 2015 04:05:05 GMT)
Full text and
rfc822 format available.
Message #12 received at 20427-done <at> debbugs.gnu.org (full text, mbox):
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
bug archived.
Request was from
Debbugs Internal Request <help-debbugs <at> gnu.org>
to
internal_control <at> debbugs.gnu.org
.
(Mon, 25 May 2015 11:24:08 GMT)
Full text and
rfc822 format available.
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.