multiple values: value1 treated extra even when not in register
Daniel Jour <[email protected]>
| Newsgroups | gmane.lisp.clisp.devel |
|---|---|
| Message-ID | <CACZHyTPrnmWiH_jHBiQG2B3oan31yMfg54SFrzD=KigHnmSo2Q@mail.gmail.com> |
I was just going over the code regarding multiple values when this caught
my attention:
In both cases, that is if value1_register is defined and when it's not,
VALUE1_EXTRA is
defined. Thus value1 is always treated extra. This affects:
STACK_to_mv
mv_to_STACK
list_to_mv
do_intern
do_find_symbol
Am I right that this is an unnoticed (thanks to the also working behavior
of the "extra"
treatment) bug?
Results of the tests seems to be not affected in any way (fails at exactly
the same test).
diff -r a6632030649a src/lispbibl.d
--- a/src/lispbibl.d Sat Apr 30 10:06:04 2016 +0200
+++ b/src/lispbibl.d Sun May 01 02:23:18 2016 +0200
@@ -11587,7 +11587,6 @@
/* Synonyms: */
#if !defined(value1_register)
#define value1 mv_space[0]
- #define VALUE1_EXTRA /* and thus has to be treated extra every time... */
#else
/* The first value mv_space[0] is stored permanently in a register: */
register object value1 __asm__(value1_register);
------------------------------------------------------------------------------
Find and fix application performance issues faster with Applications Manager
Applications Manager provides deep performance insights into multiple tiers of
your business applications. It resolves application problems quickly and
reduces your MTTR. Get your free trial!
https://ad.doubleclick.net/ddm/clk/302982198;130105516;z
_______________________________________________
clisp-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/clisp-devel