Re: DEBUG_GCSAFETY broken with g++ < 4.7

Bruno Haible <[email protected]>
Newsgroups gmane.lisp.clisp.devel
Message-ID <[email protected]>
Hi Sam,

> > The reason is that it introduces compilation errors when one attempts to use
> > DEBUG_GCSAFETY with g++ < 4.7.
> 
> The current GCC version is 6.
> Are you sure we need to support any version of GCC older than, say, 5?

RHEL 5.11 is supported until March 2017 and ships with G++ 4.1.x.
Ubuntu 12.04 is supported until April 2017 and ships with G++ 4.6.3.

> > The syntax   one_o:(o)
> > is only documented in the GCC doc [2] and is marked as "obsolete since GCC 2.5".
> > But with G++ 4.6.4 and older it's the only available syntax.
> 
> Am I the only one who finds this ironic? ("obsolete since 2.5, but the
> only option for 4.6.4 and older")

No. I find it strange too that they declared something "obsolete" and the
replacement was not available for 19 years.

> So what are you going to do?
> (obviously, I have no objections to whatever change you want to push)

I pushed it already. You should have received the automatic notification mail.

Bruno


------------------------------------------------------------------------------
Developer Access Program for Intel Xeon Phi Processors
Access to Intel Xeon Phi processor-based developer platforms.
With one year of Intel Parallel Studio XE.
Training and support from Colfax.
Order your platform today. http://sdm.link/xeonphi
_______________________________________________
clisp-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/clisp-devel
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.