From: Steven Bosscher <stevenb.gcc@gmail.com>
To: Michael Matz <matz@suse.de>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: RFC: explicitely mark out-of-scope deaths
Date: Thu, 26 May 2011 17:38:00 -0000 [thread overview]
Message-ID: <BANLkTimbaub=bFhfuz6th4smepoOKxQLMA@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.64.1105261516240.9668@wotan.suse.de>
On Thu, May 26, 2011 at 3:43 PM, Michael Matz <matz@suse.de> wrote:
> on IRC we discussed about this, here's the RFC patch. It bootstraps and
> causes some minor regressions most probably due to some missing sprinkled
> checks for the special clobber insns and sometimes due to having to adjust
> some regexps.
Just for reference... I am guessing this also supposed to help fix PR39604?
Ciao!
Steven
next prev parent reply other threads:[~2011-05-26 16:38 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-26 14:30 Michael Matz
2011-05-26 15:07 ` Jakub Jelinek
2011-05-26 15:17 ` Richard Guenther
2011-05-26 17:38 ` Steven Bosscher [this message]
2011-05-27 15:44 ` Michael Matz
2011-05-27 15:49 ` Jakub Jelinek
2011-05-27 16:45 ` Michael Matz
2011-05-26 23:49 ` Martin Jambor
2011-05-27 13:24 ` Michael Matz
2011-06-01 9:25 ` Richard Sandiford
2011-06-01 9:44 ` Richard Guenther
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='BANLkTimbaub=bFhfuz6th4smepoOKxQLMA@mail.gmail.com' \
--to=stevenb.gcc@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=matz@suse.de \
/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).