Re: workarounds around GCC miscompilation
Bruno Haible <[email protected]>
| Newsgroups | gmane.lisp.clisp.devel |
|---|---|
| Message-ID | <2326448.QktU4JVO1R@omega> |
Hi Jörg, > Some summary/stats would be nice at the end of your work: How much was caused > by individual bugs in GCC, how much by subtly broken definitions in CLISP in > some configurations. So far, at least 2/3 of the effort is spent on, like you say, "subtly broken definitions in clisp", and less than 1/3 on miscompilation by GCC. > There's no configure check for it, it's simply hard-coded. Yes. Do you have another suggestion? > (I'm not suggesting that configure should check for it, I'm just saying that it would be > useful for packagers to be able to identify work-arounds easily. What would you suggest to achieve this? Bruno ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ clisp-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/clisp-devel