From: Richard Henderson <rth@redhat.com>
To: Zack Weinberg <zack@codesourcery.com>
Cc: Richard Sandiford <rsandifo@redhat.com>,
gcc-patches@gcc.gnu.org, Andrew Pinski <pinskia@physics.uc.edu>
Subject: Re: RFC/RFA: Improve definition of ASM_OUTPUT_MEASURED_SIZE
Date: Sat, 27 Jul 2002 14:48:00 -0000 [thread overview]
Message-ID: <20020727140842.C28013@redhat.com> (raw)
In-Reply-To: <20020726215658.GC9666@codesourcery.com>; from zack@codesourcery.com on Fri, Jul 26, 2002 at 02:56:58PM -0700
On Fri, Jul 26, 2002 at 02:56:58PM -0700, Zack Weinberg wrote:
> Are there any other potentially problematic platforms, or can I go
> ahead and check the patch in?
Not that I'm aware of. Go ahead and check in the patch.
r~
next prev parent reply other threads:[~2002-07-27 21:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-25 18:22 Zack Weinberg
2002-07-25 19:56 ` Richard Henderson
2002-07-25 23:54 ` Zack Weinberg
2002-07-26 4:20 ` Richard Sandiford
2002-07-26 11:21 ` Richard Henderson
2002-07-26 16:35 ` Zack Weinberg
2002-07-27 14:48 ` Richard Henderson [this message]
2002-07-29 10:02 ` Mark Mitchell
2002-07-26 10:48 ` Mark Mitchell
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=20020727140842.C28013@redhat.com \
--to=rth@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=pinskia@physics.uc.edu \
--cc=rsandifo@redhat.com \
--cc=zack@codesourcery.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).