Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Ralf Baechle <ralf@oss.sgi.com>
To: Jun Sun <jsun@mvista.com>
Cc: linux-mips@oss.sgi.com
Subject: Re: gcc 3.x, -ansi and "static inline"
Date: Mon, 4 Feb 2002 23:21:08 +0100	[thread overview]
Message-ID: <20020204232108.A7266@dea.linux-mips.net> (raw)
In-Reply-To: <3C5EE0D0.F2CC94CE@mvista.com>; from jsun@mvista.com on Mon, Feb 04, 2002 at 11:28:16AM -0800

On Mon, Feb 04, 2002 at 11:28:16AM -0800, Jun Sun wrote:

> > On Fri, Feb 01, 2002 at 11:52:06AM -0800, Jun Sun wrote:
> > 
> > > BTW, the inclusion of "mipsregs.h" file in bitops.h seems unnecessary
> > > and caused a bunch of similar errors.
> > 
> > Indeed, it was pointless and I therefore removed it.
> 
> What about ffz()?  We can do:

Including kernel header files into user code is the actual bug but if
you think fixing that isn't an option I can certainly so a
s/inline/__inline__/

  Ralf

  reply	other threads:[~2002-02-04 22:22 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-01 19:52 gcc 3.x, -ansi and "static inline" Jun Sun
2002-02-02  9:17 ` Geert Uytterhoeven
2002-02-03 17:01 ` Ralf Baechle
2002-02-04 19:28   ` Jun Sun
2002-02-04 22:21     ` Ralf Baechle [this message]
2002-02-04 22:56       ` Jun Sun
2002-02-04 23:01         ` Ralf Baechle

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=20020204232108.A7266@dea.linux-mips.net \
    --to=ralf@oss.sgi.com \
    --cc=jsun@mvista.com \
    --cc=linux-mips@oss.sgi.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