public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Richard Guenther <richard.guenther@gmail.com>
To: Sebastian Pop <sebpop@gmail.com>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [patch][graphite] Fix PR44726: avoid uninitialized variables
Date: Wed, 30 Jun 2010 19:29:00 -0000	[thread overview]
Message-ID: <AANLkTilg6X_lbWP1p6TNxLKtLmL_hfkGPx8Qy3jxfcoS@mail.gmail.com> (raw)
In-Reply-To: <AANLkTimaOf0QwpJgKvqWt-EzGeIfk8VXSCliA0smpHCk@mail.gmail.com>

On Wed, Jun 30, 2010 at 6:32 PM, Sebastian Pop <sebpop@gmail.com> wrote:
> Hi,
>
> I will commit this patch to trunk after it passes regstrap on amd64-linux.

Bootstrap & regtest passed for me on x86_64-linux, so I applied the patch
to unbreak bootstrap for me before the freeze.

Richard.

> Sebastian Pop
> --
> AMD / Open Source Compiler Engineering / GNU Tools
>

  reply	other threads:[~2010-06-30 18:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-30 17:06 Sebastian Pop
2010-06-30 19:29 ` Richard Guenther [this message]
2010-06-30 20:50   ` Sebastian Pop

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=AANLkTilg6X_lbWP1p6TNxLKtLmL_hfkGPx8Qy3jxfcoS@mail.gmail.com \
    --to=richard.guenther@gmail.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=sebpop@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).