Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home
« Groups Home
Message from discussion MPIR and gcc-4.3.2
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
Bill Hart  
View profile  
 More options May 9 2012, 10:22 pm
From: Bill Hart <goodwillh...@googlemail.com>
Date: Wed, 9 May 2012 19:22:04 -0700 (PDT)
Local: Wed, May 9 2012 10:22 pm
Subject: Re: MPIR and gcc-4.3.2
This thread got a lot of replies on mpir-devel which didn't show up
here for various random reasons.

The gist is that the problem only occurs with debian gcc 4.3.2, and
only with fstrict-aliasing which is enabled by -O2.

There's a discussion there about what best to do about it in Sage and
MPIR. I refer you to mpir-devel for the follow up.

Bill.

On May 9, 6:28 pm, Nils Bruin <nbr...@sfu.ca> wrote:

> Both GMP and MPIR documentation complain about gcc-4.3.2, but I
> haven't seen an explicit code snippet that triggers faulty behaviour.
> Closest I found was this:

> http://trac.mpir.org/mpir_trac/ticket/291

> which indicates that at least something in "rootrem.c" goes wrong. I'd
> assume the testsuites of both GMP and MPIR pick up on the problem, so
> if you're finding everything is fine, it might be worth investigating.


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.