From: Steven Bosscher <stevenb.gcc@gmail.com>
To: Paolo Bonzini <bonzini@gnu.org>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] Fix allocation of reg_known_value
Date: Tue, 27 Nov 2012 16:32:00 -0000 [thread overview]
Message-ID: <CABu31nNap++GsPfXvvRHnk9+wXkybOWe8+Ud0Pk-9Qqt+NR1vw@mail.gmail.com> (raw)
In-Reply-To: <1354032036-32387-1-git-send-email-bonzini@gnu.org>
On Tue, Nov 27, 2012 at 5:00 PM, Paolo Bonzini wrote:
> When changing reg_known_value to a VEC, Steven sneaked in a small
> semantic change.
I don't sneak, I just tend to do stupid things from time to time ;-)
Thanks for catching this, and sorry for the breakage!
Ciao!
Steven
next prev parent reply other threads:[~2012-11-27 16:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-27 16:01 Paolo Bonzini
2012-11-27 16:32 ` Steven Bosscher [this message]
2012-11-29 22:51 Uros Bizjak
2012-11-30 10:43 ` Paolo Bonzini
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
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=CABu31nNap++GsPfXvvRHnk9+wXkybOWe8+Ud0Pk-9Qqt+NR1vw@mail.gmail.com \
--to=stevenb.gcc@gmail.com \
--cc=bonzini@gnu.org \
--cc=gcc-patches@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).