From: "Martin Schwidefsky" <schwidefsky@de.ibm.com>
To: Ulrich Drepper <drepper@redhat.com>
Cc: GNU libc hacker <libc-hacker@sources.redhat.com>
Subject: Re: s390 TLS incorporated
Date: Thu, 30 Jan 2003 09:23:00 -0000 [thread overview]
Message-ID: <OF8C4FA254.FEDB5C05-ONC1256CBE.002FC50F@de.ibm.com> (raw)
> I've added Martin's TLS stuff to the TLS document. Version 0.18
> includes it. Please check it out. A _lot_ of editing was necessary so
> I might have screwed something up.
Sorry to hear that. I had hoped to make your life easier by using
latex for the writeup. Seems like I was mistaken.
I proof-read the s390 stuff. I found some minor things:
* on page 41 the ear %r7,%a0 isn't indented correctly
* on page 42 a vertical separation line is missing
* on page 49 there is some irregular spacing in the code example
* on page 64 there is more irregular spacing in the GD->IE transition
* and finally on page 79 in the revision history another nice misspelling
of my name ;-)
I found no problem with the content of the s390 pieces.
> And on more thing: it would be good if the code sequences would get
> pseudo addresses just for the other archs. Otherwise it's not
> necessarily obvious how long an instruction has to be.
I thought about using address but decided against them because the
four/three code pieces of the examples are supposed to get scheduled
by the compiler. They in fact are never consecutive in memory because
the literal pool can not directly follow the instructions. As alternative
the size of the instructions could be added in a seperate column.
blue skies,
Martin
next reply other threads:[~2003-01-30 9:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-30 9:23 Martin Schwidefsky [this message]
2003-01-30 23:11 ` Ulrich Drepper
-- strict thread matches above, loose matches on Subject: below --
2003-01-29 19:31 Ulrich Drepper
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=OF8C4FA254.FEDB5C05-ONC1256CBE.002FC50F@de.ibm.com \
--to=schwidefsky@de.ibm.com \
--cc=drepper@redhat.com \
--cc=libc-hacker@sources.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).