All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ralf Baechle <ralf@linux-mips.org>
To: "Maciej W. Rozycki" <macro@ds2.pg.gda.pl>
Cc: Thiemo Seufer <ica2_ts@csv.ica.uni-stuttgart.de>,
	linux-mips@linux-mips.org
Subject: Re: GCCFLAGS for gcc 3.3.x (-march and _MIPS_ISA)
Date: Tue, 19 Aug 2003 14:34:53 +0200	[thread overview]
Message-ID: <20030819123453.GA17120@linux-mips.org> (raw)
In-Reply-To: <Pine.GSO.3.96.1030819140527.29184B-100000@delta.ds2.pg.gda.pl>

On Tue, Aug 19, 2003 at 02:22:37PM +0200, Maciej W. Rozycki wrote:

>  OK, I now recall <asm/asm.h> and <asm/regdef.h> as traditionally being
> often included in user assembly.  But then we should get rid of
> configuration dependency entirely, i.e. remove "#include <linux/config.h>" 
> and a CONFIG_CPU_HAS_PREFETCH dependency.  Perhaps <asm/pref.h> would be
> desireable if we don't want wasting cycles.
> 
>  It's a pity a more reasonable choice wasn't made for the location of
> these headers -- the asm and linux trees shouldn't really be used for
> userland.  For example Alpha has <alpha/regdef.h> that comes from glibc. 

I completly agree on that.  Userspace should used <sys/regdef.h>,
<sys/fpregdef.h> and <sys/asm.h> for that which are the three de-facto
standard headers used throughout the MIPS world.

As for prefetching I like your suggestion of <asm/pref.h>.  The prefetching
stuff is a Linux extension of asm.h.  Moving it to it's own header file
along with the necessary bits for <linux/prefetch.h> would make a nice
cleanup.

  Ralf

  reply	other threads:[~2003-08-19 12:35 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-12  6:26 GCCFLAGS for gcc 3.3.x (-march and _MIPS_ISA) Atsushi Nemoto
2003-08-12  6:49 ` Kumba
2003-08-12  7:06   ` Thiemo Seufer
2003-08-12  7:56     ` Kumba
2003-08-12  8:10       ` Thiemo Seufer
2003-08-12  8:26         ` Kumba
2003-08-12  9:25   ` Atsushi Nemoto
2003-08-19  3:52     ` Ralf Baechle
2003-08-12  6:51 ` Thiemo Seufer
2003-08-12 10:06   ` Atsushi Nemoto
2003-08-12 10:16     ` Thiemo Seufer
2003-08-12 15:26       ` Atsushi Nemoto
2003-08-14  3:03         ` Thiemo Seufer
2003-08-12 13:56   ` Maciej W. Rozycki
2003-08-12 14:04     ` Thiemo Seufer
2003-08-12 14:40       ` Maciej W. Rozycki
2003-08-14  3:08         ` Thiemo Seufer
2003-08-19  3:38       ` Ralf Baechle
2003-08-19 12:22         ` Maciej W. Rozycki
2003-08-19 12:34           ` Ralf Baechle [this message]
2003-08-19  3:57   ` Ralf Baechle
2003-08-19  6:41     ` Thiemo Seufer

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=20030819123453.GA17120@linux-mips.org \
    --to=ralf@linux-mips.org \
    --cc=ica2_ts@csv.ica.uni-stuttgart.de \
    --cc=linux-mips@linux-mips.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.