public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: Jes Sorensen <jes@sunsite.dk>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] rwlock and atomic_sub on ia64
Date: Mon, 13 Aug 2001 20:48:11 +0000	[thread overview]
Message-ID: <marc-linux-ia64-105590698805067@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590698805063@msgid-missing>

>>>>> "Noah" = Noah Romer <nromer@lsil.com> writes:

Noah> This is a kernel driver (linux/drivers/message/fusion). The
Noah> version in 2.4.7 isn't up to date (and doesn't contain the code
Noah> that uses rwlocks), but it's there, finally.

Ok, I saw Dave Miller checked it into his CVS tree yesterday or so.

Noah> Yep, but, for some reason, I've never gotten any complaints from
Noah> the compiler until I tried compiling on ia64. It's not a big
Noah> issue (especially since the subtracted value in this instance
Noah> should never be big enough that signed/unsigned will make a
Noah> diff), as I can just cast it to int. It just struck me as
Noah> strange that the compiler would now decide to issue a
Noah> warning. The rwlock bit is what's got me hung up.

The reason for this is most likely the compiler versions. For
Linux/ia64 you have to use at least gcc-2.96 to compile the
kernel. This compiler is a lot more picky about data types than the
older versions such as egcs-1.1.2/gcc-2.95 etc.

I'll leave the question about rwsem's to David ;)

Cheers
Jes


  parent reply	other threads:[~2001-08-13 20:48 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-13 13:55 [Linux-ia64] rwlock and atomic_sub on ia64 Noah Romer
2001-08-13 17:02 ` Jes Sorensen
2001-08-13 20:40 ` Noah Romer
2001-08-13 20:48 ` Jes Sorensen [this message]
2001-08-13 20:54 ` Noah Romer
2001-08-13 20:55 ` David Mosberger
2001-08-14 21:00 ` Noah Romer
2001-08-15 18:37 ` David Mosberger
2001-08-15 20:30 ` Noah Romer
2001-08-15 22:29 ` KOCHI Takayoshi
2001-08-16  0:25 ` David Mosberger

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=marc-linux-ia64-105590698805067@msgid-missing \
    --to=jes@sunsite.dk \
    --cc=linux-ia64@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox