From: Gabriel Dos Reis <gdr@integrable-solutions.net>
To: Daniel Berlin <dberlin@dberlin.org>
Cc: Eric Botcazou <ebotcazou@libertysurf.fr>,
Joe Buck <Joe.Buck@synopsys.COM>,
Wolfgang Bangerth <bangerth@ices.utexas.edu>,
gcc@gcc.gnu.org
Subject: Re: GCC-3.3.4 release status report
Date: Wed, 31 Mar 2004 12:42:00 -0000 [thread overview]
Message-ID: <m37jx1o1zy.fsf@uniton.integrable-solutions.net> (raw)
In-Reply-To: <F3B437E0-8295-11D8-B884-000A95DA505C@dberlin.org>
Daniel Berlin <dberlin@dberlin.org> writes:
| On Mar 30, 2004, at 4:18 PM, Eric Botcazou wrote:
|
| >> Of course the patches are not being applied "blindly".
| >
| > Well, this one is IMHO not far:
| >
| > 2004-03-12 Gabriel Dos Reis <gdr@integrable-solutions.net>
| >
| > Backport:
| > 2004-03-13 Eric Botcazou <ebotcazou@libertysurf.fr>
| > PR middle-end/14470
| > * expr.c (store_expr): Call emit_queue before generating the move
| > from the temporary to the original target. Protect the temporary
| > from emit_queue.
| >
| >
|
| He also backported a patch from the future, which is odd.
If you look at the audit trail of 14470 you'll see that Eric commented
(#17) on 2004-03-11 06:34 that the patch was approved for mainline.
On 2004-03-13, I tested and applied the patch, which contains the date
you see in comment #19 (not 2004-03-13).
-- Gaby
next prev parent reply other threads:[~2004-03-31 9:40 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-30 0:20 Wolfgang Bangerth
2004-03-30 18:56 ` Gabriel Dos Reis
2004-03-30 19:19 ` Theodore Papadopoulo
2004-03-30 23:59 ` Joe Buck
2004-03-31 2:50 ` Eric Botcazou
2004-03-31 3:10 ` Daniel Berlin
2004-03-31 11:24 ` Eric Botcazou
2004-03-31 12:42 ` Gabriel Dos Reis [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-03-27 21:26 Gabriel Dos Reis
2004-03-29 19:17 ` Joe Buck
2004-03-30 0:24 ` Richard Guenther
2004-03-30 18:46 ` Gabriel Dos Reis
2004-03-31 1:15 ` Joe Buck
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=m37jx1o1zy.fsf@uniton.integrable-solutions.net \
--to=gdr@integrable-solutions.net \
--cc=Joe.Buck@synopsys.COM \
--cc=bangerth@ices.utexas.edu \
--cc=dberlin@dberlin.org \
--cc=ebotcazou@libertysurf.fr \
--cc=gcc@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).