All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tom Leete <tleete@mountain.net>
To: Ishikawa <ishikawa@yk.rim.or.jp>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.4.0-test-11: K7 compile error: `current' missing in string macro.
Date: Fri, 24 Nov 2000 20:58:40 -0500	[thread overview]
Message-ID: <3A1F1CD0.E2FCCE27@mountain.net> (raw)
In-Reply-To: <3A1F0DF0.AECF7057@yk.rim.or.jp>

Ishikawa wrote:
> 
> 2.4.0-test-11: K7 compile error: `current' missing in string macro.
> 
> Symptom:
> 2.4.0-test11 won't compile with K7 if we choose it for CPU.
> 
> The compile error is attached at the end.
> 
> The same config except for CPU (AMD K6) works.
> The diff of config is shown immediately below.
> (I saved the old config from some early test-1x series
> compilation.)
> 
[...]
> 
> HALF-HEARTED FIX suggestion.:
> 
> I looked around and found asm/current.h had this
> #define current get_current()
> 
> 
> QUESTION: Shouldn't this code  be enabled for AMD K6-III
> (not K7), too? (It would boost the performance on this CPU if so.)
> Or does K6-III lack some instructions of 3D-Now (available
> in K7, Athlon or Duron) and so can't use these macros?
> 
> Either way, asm/current.h needs to be included
> somewhere (probably after the include statements quoted above?)

Either deselect SMP or see the patch I posted here in May. If you just keep
adding headers for stuff in_interrupt() needs, you soon hit a circular
dependency.

Tom
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

      reply	other threads:[~2000-11-25  2:37 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-11-25  0:55 2.4.0-test-11: K7 compile error: `current' missing in string macro Ishikawa
2000-11-25  1:58 ` Tom Leete [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=3A1F1CD0.E2FCCE27@mountain.net \
    --to=tleete@mountain.net \
    --cc=ishikawa@yk.rim.or.jp \
    --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 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.