PARI/GP Bug report logs - #1237
undefined behaviour in pari_init_parser

Full log

🔗 View this message in rfc822 format

X-Loop: allomber@math.u-bordeaux.fr
From: allomber@math.u-bordeaux.fr (PARI/GP Bug Tracking System)
To: Julian Taylor <jtaylor.debian@googlemail.com>
Subject: Bug#1237 acknowledged by developer
         (Re: Bug#1237: undefined behaviour in pari_init_parser)
Message-ID: <handler.1237.D1237.13285700585381.notifdone@pari.math.u-bordeaux.fr>
In-Reply-To: <4E5E52C5.4050702@googlemail.com>
References: <20120206231411.GD7664@yellowpig> <4E5E52C5.4050702@googlemail.com>
X-PARI/GP-PR-Message: they-closed 1237
X-PARI/GP-PR-Package: pari
X-PARI/GP-PR-Keywords: 
Reply-To: 1237@pari.math.u-bordeaux.fr

This is an automatic notification regarding your Bug report
#1237: undefined behaviour in pari_init_parser,
which was filed against the pari package.

It has been closed by one of the developers, namely
Bill Allombert <Bill.Allombert@math.u-bordeaux1.fr>.

Their explanation is attached below.  If this explanation is
unsatisfactory and you have not received a better one in a separate
message then please contact the developer, by replying to this email.

Bill Allombert
(administrator, PARI/GP bugs database)

Received: (at 1237-done) by pari.math.u-bordeaux.fr; 6 Feb 2012 23:14:18 +0000
From Bill.Allombert@math.u-bordeaux1.fr Tue Feb 07 00:14:18 2012
Received: from smtp1-g21.free.fr ([212.27.42.1])
	by pari.math.u-bordeaux1.fr with esmtp (Exim 4.72)
	(envelope-from <Bill.Allombert@math.u-bordeaux1.fr>)
	id 1RuXlK-0001Ok-GR
	for 1237-done@pari.math.u-bordeaux.fr; Tue, 07 Feb 2012 00:14:18 +0100
Received: from yellowpig (unknown [IPv6:2a01:e35:2f45:9a0:223:14ff:fe3e:4490])
	by smtp1-g21.free.fr (Postfix) with ESMTP id 0CFF89400E1;
	Tue,  7 Feb 2012 00:14:12 +0100 (CET)
Received: from bill by yellowpig with local (Exim 4.72)
	(envelope-from <Bill.Allombert@math.u-bordeaux1.fr>)
	id 1RuXlD-0005WQ-NK; Tue, 07 Feb 2012 00:14:11 +0100
Date: Tue, 7 Feb 2012 00:14:11 +0100
From: Bill Allombert <Bill.Allombert@math.u-bordeaux1.fr>
To: Julian Taylor <jtaylor.debian@googlemail.com>
Cc: 1237-done@pari.math.u-bordeaux.fr
Subject: Re: Bug#1237: undefined behaviour in pari_init_parser
Message-ID: <20120206231411.GD7664@yellowpig>
References: <4E5E52C5.4050702@googlemail.com>
 <20110901202245.GH17070@yellowpig>
 <4E5FF27B.5080600@googlemail.com>
 <20110902165738.GM17070@yellowpig>
 <20110913144151.GE6199@yellowpig>
 <20120126162508.GA18262@yellowpig>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20120126162508.GA18262@yellowpig>
User-Agent: Mutt/1.5.20 (2009-06-14)

On Thu, Jan 26, 2012 at 05:25:08PM +0100, Bill Allombert wrote:
> On Tue, Sep 13, 2011 at 04:41:51PM +0200, Bill Allombert wrote:
> > On Fri, Sep 02, 2011 at 06:57:38PM +0200, Bill Allombert wrote:
> > > On Thu, Sep 01, 2011 at 11:00:43PM +0200, Julian Taylor wrote:
> > > 
> > > Well, you can try the attached patch which work around the compiler issue without
> > > breaking the ABI (tested on sparc).
> > 
> > Hello Julian, 
> > I have uploaded a new Debian package that includes this patch and it was built correctly
> > on all platform, as you can see 
> > <https://buildd.debian.org/status/package.php?p=pari>
> > this includes armel and sparc. 
> > Do you still have issues on armel ?
> > 
> > A technical note: it is possible that stack_init is not standard compliant, but it
> > should be possible to rewrite it in a standard compliant according to
> > <http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49330#c8>
> > However gcc-4.6 bug PR49330 is still open so PARI would still be miscompiled.
> 
> Hello Julian,
> 
> Sorry for the long delay,
> 
> I just fixed stack_base to be standard compliant. It seems actually improve things
> with the version of gcc I tried (Debian 4.6.2-12). It did not with older versions.
> 
> This is is revision c3f6b58983. This is backported in PARI 2.5.1 in rev ee8e36931.
> PARI 2.5.1 will be released soon.

I have just released PARI 2.5.1, so I close this report.
Cheers,
Bill.

Send a report that this bug log contains spam.