From: Thiemo Seufer <ica2_ts@csv.ica.uni-stuttgart.de>
To: "Maciej W. Rozycki" <macro@linux-mips.org>
Cc: Richard Sandiford <rsandifo@redhat.com>, binutils@sources.redhat.com
Subject: Re: [patch] MIPS: Fix synthesized doubleword transfers (ping)
Date: Wed, 02 Mar 2005 02:22:00 -0000 [thread overview]
Message-ID: <20050302022212.GB1272@rembrandt.csv.ica.uni-stuttgart.de> (raw)
In-Reply-To: <Pine.LNX.4.61L.0502251605380.9216@blysk.ds.pg.gda.pl>
Maciej W. Rozycki wrote:
[snip]
> > [ Although, as is probably clear from earlier messages, my preference is
> > to keep things the way they are, and require any symbolic component to
> > be 8-byte aligned. I've never heard of any practical problems with that
> > restriction. OTOH, after the above, I don't have any new data or
> > arguments to add, so I'll shut up now ;) ]
FWIW, I agree with Richard.
> It works with native 64-bit transfers -- why should it be broken with
> their 32-bit macro counterparts?
>
> Actually I wouldn't mind ditching these macros altogether. ;-)
They are IMHO a bad idea (but not bad enough to remove them).
Thiemo
prev parent reply other threads:[~2005-03-02 2:22 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-24 22:30 Maciej W. Rozycki
2005-02-24 22:57 ` Richard Sandiford
[not found] ` <mailpost.1109279149.22995@news-sj1-1>
2005-02-24 23:42 ` cgd
2005-02-25 0:04 ` Richard Sandiford
2005-02-25 1:23 ` Richard Sandiford
2005-02-25 2:17 ` cgd
2005-02-25 13:36 ` Richard Sandiford
2005-02-26 0:02 ` Maciej W. Rozycki
2005-02-25 20:25 ` Maciej W. Rozycki
2005-02-25 16:12 ` Richard Sandiford
2005-02-26 0:10 ` Maciej W. Rozycki
2005-03-02 2:22 ` Thiemo Seufer [this message]
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=20050302022212.GB1272@rembrandt.csv.ica.uni-stuttgart.de \
--to=ica2_ts@csv.ica.uni-stuttgart.de \
--cc=binutils@sources.redhat.com \
--cc=macro@linux-mips.org \
--cc=rsandifo@redhat.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).