From: Eric Botcazou <ebotcazou@adacore.com>
To: "Richard Guenther" <richard.guenther@gmail.com>
Cc: gcc-patches@gcc.gnu.org, "Paolo Bonzini" <bonzini@gnu.org>,
"Andrew Pinski" <pinskia@gmail.com>,
"Mark Mitchell" <mark@codesourcery.com>
Subject: Re: PR/32004, tree-ssa caused in/out asm constraints to often need reloads
Date: Mon, 09 Jul 2007 13:36:00 -0000 [thread overview]
Message-ID: <200707091536.04591.ebotcazou@adacore.com> (raw)
In-Reply-To: <84fc9c000707090554h4eab439di66e1d1966d3122af@mail.gmail.com>
> There is no formal need of approval for porting regression fixes from the
> trunk to release branches. If this is good or bad is another question.
Well, there is at least an implicit one. Note that Paolo did explicitly
request approval for the 4.2 branch, and I don't think we should be more
lax for the 4.1 branch than for the 4.2 branch, quite the contrary.
--
Eric Botcazou
next prev parent reply other threads:[~2007-07-09 13:33 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-05 10:54 Paolo Bonzini
[not found] ` <84fc9c000707050401h46157b0fye4b32c3e6b1c8063@mail.gmail.com>
2007-07-05 11:48 ` Paolo Bonzini
2007-07-05 18:34 ` Mark Mitchell
2007-07-05 19:39 ` Paolo Bonzini
2007-07-05 20:24 ` Mark Mitchell
2007-07-05 20:15 ` Paolo Bonzini
2007-07-07 16:29 ` Eric Botcazou
2007-07-07 18:24 ` Andrew Pinski
2007-07-07 18:30 ` Eric Botcazou
2007-07-09 2:23 ` Paolo Bonzini
2007-07-09 6:52 ` Eric Botcazou
2007-07-09 12:09 ` Paolo Bonzini
2007-07-09 12:32 ` Paolo Bonzini
2007-07-09 12:40 ` Richard Guenther
2007-07-09 13:01 ` Eric Botcazou
2007-07-09 13:01 ` Richard Guenther
2007-07-09 13:36 ` Eric Botcazou [this message]
2007-07-09 13:12 ` Paolo Bonzini
2007-07-09 13:23 ` Andrew Pinski
2007-07-09 13:45 ` Eric Botcazou
2007-07-09 15:33 ` Paolo Bonzini
2007-07-09 17:25 ` Eric Botcazou
2007-07-09 14:00 ` Eric Botcazou
2007-07-13 9:48 ` Paolo Bonzini
2007-07-13 13:42 ` Eric Botcazou
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=200707091536.04591.ebotcazou@adacore.com \
--to=ebotcazou@adacore.com \
--cc=bonzini@gnu.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=mark@codesourcery.com \
--cc=pinskia@gmail.com \
--cc=richard.guenther@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).