Greetings, and thanks so much for looking into this! As always, a small code example is worth its weight in gold. I'm assuming we're referring to code emitted by the GCL lisp compiler? If not, the task is considerably simpler. In either case, we've adapted to gcc changes before and can do so again. 4.4 is not yet in Debian sid, apparently.
BTW, I've made considerable progress on your very helpful patches and will have more to report soon. Take care, Jerry James <loganje...@gmail.com> writes: > Recently, GCC 4.4.0 went into Fedora Rawhide (which will become Fedora > 11). Thereafter, the GCL build started failing. Investigation shows > that this is because GCC 4.4.0 is much more aggressive than its > predecessors about exploiting the ANSI C strict aliasing rules. GCL > fails to follow those rules in several places, so GCC emitted code > that caused runtime failures. > > I have fixed the build for now by passing -fno-strict-aliasing to GCC. > However, that is not a good long-term solution, since it prevents GCC > from emitting the most optimized code possible. Over the next couple > of weeks, I will try to look at how to fix up the C code to obey the > ANSI C rules. If anybody is interested in participating in that, let > me know so we don't duplicate work. > > Regards, > -- > Jerry James > http://loganjerry.googlepages.com/ > > > _______________________________________________ > Gcl-devel mailing list > Gcl-devel@gnu.org > http://lists.gnu.org/mailman/listinfo/gcl-devel > > > > -- Camm Maguire c...@maguirefamily.org ========================================================================== "The earth is but one country, and mankind its citizens." -- Baha'u'llah _______________________________________________ Gcl-devel mailing list Gcl-devel@gnu.org http://lists.gnu.org/mailman/listinfo/gcl-devel
