public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Martin Schwidefsky <schwidefsky@de.ibm.com>
To: "linux-os (Dick Johnson)" <linux-os@analogic.com>
Cc: linux-kernel@vger.kernel.org, heiko.carstens@de.ibm.com
Subject: Re: [patch 5/6] s390: .align 4096 statements in head.S
Date: Tue, 18 Jul 2006 16:10:42 +0200	[thread overview]
Message-ID: <1153231842.13773.6.camel@localhost> (raw)
In-Reply-To: <Pine.LNX.4.61.0607180929340.12146@chaos.analogic.com>

On Tue, 2006-07-18 at 09:33 -0400, linux-os (Dick Johnson) wrote:
> >> It looks like
> >> you wrote something in 'C' and tried to use its assembly code.
> Yes, I know exactly what I am saying and I mentioned the reference
> to 'C' because the ".Labels" start with ".L" as 'C' does it. Humans
> generally use human-readable names.

You postulated that we have converted some C code and tried to use the
resulting assembly code. We did not. Do not make assumptions.

> If you BOTHERED to read the rest of the email, I instructed one
> how to use the assembler 'gas' so I certainly know that it is not
> 'C'. Thank you.

Thank you very much for your kind instruction how to use the assembler.
The .fill statements are there for the definition of the SCCB that finds
out about the memory size of the machine. An SCCB has a peculiar format,
to make it independent of the location the .fill statements do make
sense, even if they fill up with zeroes.

-- 
blue skies,
  Martin.

Martin Schwidefsky
Linux for zSeries Development & Services
IBM Deutschland Entwicklung GmbH

"Reality continues to ruin my life." - Calvin.



      reply	other threads:[~2006-07-18 14:10 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-18 11:56 [patch 5/6] s390: .align 4096 statements in head.S Martin Schwidefsky
2006-07-18 12:43 ` linux-os (Dick Johnson)
2006-07-18 12:51   ` Martin Schwidefsky
2006-07-18 13:33     ` linux-os (Dick Johnson)
2006-07-18 14:10       ` Martin Schwidefsky [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=1153231842.13773.6.camel@localhost \
    --to=schwidefsky@de.ibm.com \
    --cc=heiko.carstens@de.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-os@analogic.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