public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Paolo Bonzini <bonzini@gnu.org>
To: Uros Bizjak <ubizjak@gmail.com>
Cc: gcc-patches@gcc.gnu.org, Steven Bosscher <stevenb.gcc@gmail.com>
Subject: Re: [PATCH] Fix allocation of reg_known_value
Date: Fri, 30 Nov 2012 10:43:00 -0000	[thread overview]
Message-ID: <50B88CDF.6030508@gnu.org> (raw)
In-Reply-To: <CAFULd4ZG42Y-yhfKdON2kaheU7LgzMHkspmLLMbCBFT1U-xhpg@mail.gmail.com>

Il 29/11/2012 23:47, Uros Bizjak ha scritto:
> This one-liner causes following runtime test failure [1] for
> alphaev68-linux-gnu:
> 
> FAIL: gfortran.fortran-torture/execute/save_1.f90 execution,  -O2
> FAIL: gfortran.fortran-torture/execute/save_1.f90 execution,  -O2
> -fomit-frame-pointer -finline-functions
> FAIL: gfortran.fortran-torture/execute/save_1.f90 execution,  -O2
> -fomit-frame-pointer -finline-functions -funroll-loops
> FAIL: gfortran.fortran-torture/execute/save_1.f90 execution,  -O2
> -fbounds-check
> 
> The patch miscompiles libgfortran library.
> 
> I will provide more info tomorrow, any hint what/where should I look
> for differences?

Anywhere.  The bug disabled a large part of alias analysis.

Perhaps you can bisect it and backport the fix along the steps.

Paolo

  reply	other threads:[~2012-11-30 10:39 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-29 22:51 Uros Bizjak
2012-11-30 10:43 ` Paolo Bonzini [this message]
2012-11-30 10:43   ` Steven Bosscher
2012-11-30 12:34     ` Uros Bizjak
2012-11-30 13:17       ` Uros Bizjak
2012-11-30 14:54       ` Steven Bosscher
2012-11-30 15:10         ` Steven Bosscher
2012-11-30 15:57         ` Uros Bizjak
  -- strict thread matches above, loose matches on Subject: below --
2012-11-27 16:01 Paolo Bonzini
2012-11-27 16:32 ` Steven Bosscher

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=50B88CDF.6030508@gnu.org \
    --to=bonzini@gnu.org \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=stevenb.gcc@gmail.com \
    --cc=ubizjak@gmail.com \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).