Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Ralf Baechle <ralf@linux-mips.org>
To: Philippe De Swert <philippedeswert@scarlet.be>
Cc: tom <tom@voda.cz>, linux-mips <linux-mips@linux-mips.org>
Subject: Re: [Fwd: kernel compilation fails]
Date: Thu, 16 Jun 2005 11:20:55 +0100	[thread overview]
Message-ID: <20050616102054.GG5202@linux-mips.org> (raw)
In-Reply-To: <II68V7$710BD802DB90EFADDBE27A92E7C5B2C2@scarlet.be>

On Thu, Jun 16, 2005 at 10:54:43AM +0100, Philippe De Swert wrote:

> Basically 2.4.18 code is too old to compile as is with gcc 3.3.4. The
> assembler code needs to be inlined with a different syntax. Just look at
> similar files to see how it is done.

Not true.  Gcc 3.3 is probably even is the most commonly used compiler
with 2.4-based systems.  Builds with gcc 3.4 will fail for some 2.4
kernel configurations but at the very least throw loads of warnings.

> As a quick hint here is some code to show how it should look like.
> 
> 
>         __asm__(".set\tmips3\n\t"
>                 "wait\n\t"
>                 ".set\tmips0");
> 
> Notice the \n and \t parts. You are probabely missing those.

Actually more and more code it being formatted using tabs instead of the
\t escape sequence for readability.

  Ralf

  reply	other threads:[~2005-06-16 10:24 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-16  9:54 Re:[Fwd: kernel compilation fails] Philippe De Swert
2005-06-16 10:20 ` Ralf Baechle [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-06-16  9:37 [Fwd: " Tomáš Vrána

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=20050616102054.GG5202@linux-mips.org \
    --to=ralf@linux-mips.org \
    --cc=linux-mips@linux-mips.org \
    --cc=philippedeswert@scarlet.be \
    --cc=tom@voda.cz \
    /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