public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Helmut Jarausch <jarausch@igpm.rwth-aachen.de>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Backgammon (GNU) anybody
Date: Sun, 14 Jun 2015 10:53:36 +0200	[thread overview]
Message-ID: <7ZPZMl7N3so54cL7R2c5lD@Bg7K9O55tOJHPc95JkXRk> (raw)
In-Reply-To: <BD802200-EBE4-4092-AACB-071258A9A336@stellar.eclipse.co.uk> (from stroller@stellar.eclipse.co.uk on Sat Jun 13 17:42:10 2015)

On 06/13/2015 05:42:10 PM, Stroller wrote:
> 
> On Fri, 12 June 2015, at 5:03 pm, Helmut Jarausch <jarausch@skynet.be>
> wrote:
> > On 06/11/2015 09:32:23 PM, Grant Edwards wrote:
> > 
> >> I got curious and just did "emerge -av gnubg". It compiled and
> >> installed fine, and it seems to work.  
> > 
> > Many thanks, it turnt out to be a strange problem.
> > 
> > When compiled with gcc-5.1.0 and -O2, gnubg goes into a tight loop
> within memset 
> > even before function main is entered.
> > 
> > When compiled with gcc-5.1.0 and -O1, gnubg gets a segment fault
> from within memset 
> > even before function main is entered.
> > 
> > When compiled with gcc-5.1.0 and -O0, it works just fine.
> > 
> > Stepping back to gcc-4.9.2 it succeeds even when compiled with -O2.
> > 
> > So, it looks like a compiler error of gcc-5.1.0
> 
> You should report this upstream. To gcc, I think?
> 
As I found out, it has been fixed already. Not for gcc-5.1 but with a recent snapshot of gcc-5 as well as gcc-6.




      reply	other threads:[~2015-06-14  8:53 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-11 16:01 [gentoo-user] Backgammon (GNU) anybody Helmut Jarausch
2015-06-11 19:19 ` [gentoo-user] " Grant Edwards
2015-06-11 19:32   ` Grant Edwards
2015-06-12 16:03     ` Helmut Jarausch
2015-06-13 15:42       ` [gentoo-user] " Stroller
2015-06-14  8:53         ` Helmut Jarausch [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=7ZPZMl7N3so54cL7R2c5lD@Bg7K9O55tOJHPc95JkXRk \
    --to=jarausch@igpm.rwth-aachen.de \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox