From: David Mosberger <davidm@napali.hpl.hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: Kill warnings in 2.6.6
Date: Fri, 21 May 2004 20:23:46 +0000 [thread overview]
Message-ID: <16558.25938.462552.233122@napali.hpl.hp.com> (raw)
In-Reply-To: <E1BQFaq-0003bB-KT@wombat.disy.cse.unsw.edu.au>
> -#define cond_syscall(x) asmlinkage long x() __attribute__((weak,alias("sys_ni_syscall")));
> +#define cond_syscall(x) asmlinkage long x(void) __attribute__((weak,alias("sys_ni_syscall")));
I made this change now. The Intel compiler certainly compiles it fine
and it gets rid of the last remaining large blob of annoying warning
messages in sys.c. I didn't try building the entire kernel with the
Intel compiler, but in the unlikely event that Peter's version leads
to link-time-problems, we can fix that later, when Intel makes the
script available needed to compile the kernel (hint, hint... ;-).
--david
prev parent reply other threads:[~2004-05-21 20:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-19 1:10 Kill warnings in 2.6.6 Peter Chubb
2004-05-19 21:02 ` David Mosberger
2004-05-20 1:10 ` David Mosberger
2004-05-20 4:55 ` Peter Chubb
2004-05-20 5:10 ` David Mosberger
2004-05-21 20:23 ` David Mosberger [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=16558.25938.462552.233122@napali.hpl.hp.com \
--to=davidm@napali.hpl.hp.com \
--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