From: Ralf Baechle <ralf@oss.sgi.com>
To: "Maciej W. Rozycki" <macro@ds2.pg.gda.pl>
Cc: Guido Guenther <agx@sigxcpu.org>, linux-mips@oss.sgi.com
Subject: Re: 2.4.18: pgtable.h compile fix
Date: Tue, 25 Jun 2002 10:54:36 +0200 [thread overview]
Message-ID: <20020625105436.A16439@dea.linux-mips.net> (raw)
In-Reply-To: <Pine.GSO.3.96.1020624174346.22509N-100000@delta.ds2.pg.gda.pl>; from macro@ds2.pg.gda.pl on Mon, Jun 24, 2002 at 05:54:28PM +0200
On Mon, Jun 24, 2002 at 05:54:28PM +0200, Maciej W. Rozycki wrote:
> > > MIPS64 lags behind a bit due to less interest/testing. Note that you
> > > should use "__ASSEMBLY__" to guard assembly-unsafe parts of headers.
> >
> > _LANGUAGE_ASSEMBLY is the traditional MIPS cpp symbol to indicate assembler
> > source code.
>
> Well, but the rest of the kernel uses "__ASSEMBLY__", that's defined in
> the top-level Makefile. What's the point in being different?
>
> Also it doesn't seem to work for me -- the rules in specs look broken:
>
> $ mipsel-linux-gcc -E -dM -xassembler-with-cpp /dev/null | grep LANGUAGE
> #define __LANGUAGE_C 1
> #define _LANGUAGE_C 1
> #define LANGUAGE_C 1
>
> thus it cannot be considered reliable.
The machanism guesses the language based on the source file name extension:
[ralf@dea tmp]$ echo -n > c.c && mips-linux-gcc -E -dM -xassembler-with-cpp c.c | grep LANG
#define __LANGUAGE_C 1
#define _LANGUAGE_C 1
#define LANGUAGE_C 1
[ralf@dea tmp]$ echo -n > c.S && mips-linux-gcc -E -dM c.S | grep LANG
#define LANGUAGE_ASSEMBLY 1
#define _LANGUAGE_ASSEMBLY 1
#define __LANGUAGE_ASSEMBLY 1
[ralf@dea tmp]$
Buggy? Yes ...
Ralf
prev parent reply other threads:[~2002-06-25 8:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-23 12:58 2.4.18: pgtable.h compile fix Guido Guenther
2002-06-24 8:11 ` Ralf Baechle
2002-06-26 13:23 ` Guido Guenther
2002-06-24 8:30 ` Maciej W. Rozycki
2002-06-24 13:33 ` Ralf Baechle
2002-06-24 15:54 ` Maciej W. Rozycki
2002-06-25 8:54 ` Ralf Baechle [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=20020625105436.A16439@dea.linux-mips.net \
--to=ralf@oss.sgi.com \
--cc=agx@sigxcpu.org \
--cc=linux-mips@oss.sgi.com \
--cc=macro@ds2.pg.gda.pl \
/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