From: Carlos O'Donell <carlos@baldric.uwo.ca>
To: Matthew Wilcox <willy@debian.org>
Cc: John David Anglin <dave@hiauly1.hia.nrc.ca>,
parisc-linux@lists.parisc-linux.org, tausq@debian.org
Subject: Re: [parisc-linux] glibc 2.3.1 - It's alive! - patches
Date: Mon, 11 Nov 2002 13:20:12 -0500 [thread overview]
Message-ID: <20021111182012.GN8848@systemhalted> (raw)
In-Reply-To: <20021111180016.D29998@parcelfarce.linux.theplanet.co.uk>
On Mon, Nov 11, 2002 at 06:00:16PM +0000, Matthew Wilcox wrote:
> On Mon, Nov 11, 2002 at 12:36:25PM -0500, John David Anglin wrote:
> > > Looks like we need some __asm format fixes?
> >
> > These are the changes that I had for glibc-2.2.5-14 to build with gcc-3.3.
> > The string literal change makes the asms ugly but I think we have to live
> > with it. I don't know the ins and outs of why the change was necessary
> > but I know the cpp people will not change back.
>
> > + stw %rp,-20(%sp)\n\
> > + stwm %r4,64(%sp)\n\
> > + stw %r19,-32(%sp)\n\
>
> By and large we've preferred the following style which is less ugly, IMO:
>
> " stw %rp,-20(%sp)\n"
> " stwm %r4,64(%sp)\n"
> " stw %r19,-32(%sp)\n"
>
All of Uli's fixes have been the ugly way, though I'll change
pt-initfini the nice and pretty way and hope they take the patch :)
c.
next prev parent reply other threads:[~2002-11-11 18:20 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-11 1:05 [parisc-linux] glibc 2.3.1 - It's alive! - patches Carlos O'Donell
2002-11-11 1:19 ` John David Anglin
2002-11-11 17:12 ` Carlos O'Donell
2002-11-11 17:36 ` John David Anglin
2002-11-11 18:00 ` Matthew Wilcox
2002-11-11 18:20 ` Carlos O'Donell [this message]
2002-11-11 18:58 ` Carlos O'Donell
2002-11-11 20:42 ` Carlos O'Donell
2002-11-11 20:57 ` John David Anglin
2002-11-11 21:17 ` Carlos O'Donell
2002-11-11 21:33 ` John David Anglin
2002-11-12 5:31 ` [parisc-linux] simple testcase for binutils visibility problem Randolph Chung
2002-11-12 5:58 ` John David Anglin
2002-11-11 21:16 ` [parisc-linux] glibc 2.3.1 - It's alive! - patches Carlos O'Donell
2002-11-11 22:36 ` John David Anglin
2002-11-11 22:44 ` Carlos O'Donell
2002-11-11 22:53 ` John David Anglin
2002-11-11 23:27 ` Carlos O'Donell
2002-11-12 0:22 ` John David Anglin
2002-11-12 1:23 ` Carlos O'Donell
2002-11-12 4:13 ` John David Anglin
2002-11-12 15:44 ` John David Anglin
2002-11-12 17:42 ` Jim Hull
2002-11-12 17:53 ` John David Anglin
2002-11-12 18:43 ` Jim Hull
2002-11-12 19:02 ` John David Anglin
2002-11-12 19:31 ` Jim Hull
2002-11-12 19:38 ` John David Anglin
2002-11-13 19:22 ` Carlos O'Donell
2002-11-13 20:16 ` John David Anglin
2002-11-17 21:54 ` John David Anglin
2002-11-18 16:12 ` Carlos O'Donell
2002-11-18 17:42 ` John David Anglin
2002-11-18 19:30 ` Carlos O'Donell
2002-11-18 19:44 ` John David Anglin
2002-11-11 1:21 ` Matthew Wilcox
2002-11-11 1:32 ` John David Anglin
2002-11-11 1:49 ` Carlos O'Donell
2002-11-11 3:45 ` John David Anglin
2002-11-11 4:26 ` John David Anglin
2002-11-11 15:03 ` Carlos O'Donell
2002-11-11 15:47 ` John David Anglin
2002-11-11 16:26 ` Carlos O'Donell
2002-11-11 17:25 ` John David Anglin
2002-11-11 17:37 ` Carlos O'Donell
2002-11-11 17:46 ` John David Anglin
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=20021111182012.GN8848@systemhalted \
--to=carlos@baldric.uwo.ca \
--cc=dave@hiauly1.hia.nrc.ca \
--cc=parisc-linux@lists.parisc-linux.org \
--cc=tausq@debian.org \
--cc=willy@debian.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