From: Sam Ravnborg <sam@ravnborg.org>
To: linux-arch@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [RFC] Consistently use the name asm-offsets.h
Date: Thu, 8 Sep 2005 23:47:42 +0200 [thread overview]
Message-ID: <20050908214741.GA16421@mars.ravnborg.org> (raw)
In-Reply-To: <20050908211539.GA24714@mars.ravnborg.org>
mips has it own private gen-asm-offset macro,
The important part being:
sed -ne "/^@@@/s///p"; \
compared to the generic one:
sed -ne "/^->/{s:^->\([^ ]*\) [\$$#]*\([^ ]*\) \(.*\):#define \1 \2 /* \3 */:; s:->::; p;}"; \
I wonder why the assembly for mips is so different...
So for now two architectures needs special care: mips and ia64.
Sam
next prev parent reply other threads:[~2005-09-08 21:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-08 21:15 [RFC] Consistently use the name asm-offsets.h Sam Ravnborg
2005-09-08 21:47 ` Sam Ravnborg [this message]
2005-09-09 11:17 ` Ralf Baechle
2005-09-09 11:25 ` Jan-Benedict Glaw
-- strict thread matches above, loose matches on Subject: below --
2005-09-08 21:39 Luck, Tony
2005-09-08 22:09 ` Brian Gerst
2005-09-09 8:04 ` Paul Jackson
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=20050908214741.GA16421@mars.ravnborg.org \
--to=sam@ravnborg.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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