public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/47903] [4.5 Regression] var-tracking.c: valgrind error
Date: Wed, 20 Jun 2012 13:56:00 -0000	[thread overview]
Message-ID: <bug-47903-4-AkmHC67i5F@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-47903-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47903

--- Comment #7 from Richard Guenther <rguenth at gcc dot gnu.org> 2012-06-20 13:56:01 UTC ---
Author: rguenth
Date: Wed Jun 20 13:55:44 2012
New Revision: 188834

URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=188834
Log:
2012-06-20  Richard Guenther  <rguenther@suse.de>

    Backport from mainline
    2010-12-18  Jakub Jelinek  <jakub@redhat.com>

    PR tree-optimization/46985
    * tree-scalar-evolution.c (instantiate_scev_r): If chrec is NULL,
    return it immediately.

    * gfortran.dg/pr46985.f90: New test.

    2011-02-18  Jakub Jelinek  <jakub@redhat.com>

    PR debug/47780
    * cfgexpand.c (expand_debug_expr) <case SSA_NAME>: Call copy_rtx to
    avoid invalid rtx sharing.

    * gcc.target/i386/pr47780.c: New test.

    2011-02-27  Jakub Jelinek  <jakub@redhat.com>

    PR middle-end/47903
    * real.c (real_arithmetic) <case PLUS_EXPR, MINUS_EXPR,
    MULT_EXPR, RDIV_EXPR>: Clear padding bits in *r first if
    r isn't op0 nor op1.

Added:
    branches/gcc-4_5-branch/gcc/testsuite/gcc.target/i386/pr47780.c
    branches/gcc-4_5-branch/gcc/testsuite/gfortran.dg/pr46985.f90
Modified:
    branches/gcc-4_5-branch/gcc/ChangeLog
    branches/gcc-4_5-branch/gcc/cfgexpand.c
    branches/gcc-4_5-branch/gcc/real.c
    branches/gcc-4_5-branch/gcc/testsuite/ChangeLog
    branches/gcc-4_5-branch/gcc/tree-scalar-evolution.c


  parent reply	other threads:[~2012-06-20 13:56 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-26  9:55 [Bug c++/47903] New: " dcb314 at hotmail dot com
2011-02-26 15:42 ` [Bug middle-end/47903] " jakub at gcc dot gnu.org
2011-02-26 16:04 ` jakub at gcc dot gnu.org
2011-02-26 16:23 ` [Bug middle-end/47903] [4.5/4.6 Regression] " jakub at gcc dot gnu.org
2011-02-27 19:45 ` jakub at gcc dot gnu.org
2011-02-27 19:46 ` [Bug middle-end/47903] [4.5 " jakub at gcc dot gnu.org
2011-03-25 20:10 ` jakub at gcc dot gnu.org
2011-06-27 16:36 ` jakub at gcc dot gnu.org
2011-10-10 12:43 ` rguenth at gcc dot gnu.org
2012-06-20 12:57 ` rguenth at gcc dot gnu.org
2012-06-20 13:56 ` rguenth at gcc dot gnu.org [this message]
2012-06-20 14:49 ` rguenth at gcc dot gnu.org

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=bug-47903-4-AkmHC67i5F@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).