From: Andi Kleen <ak@suse.de>
To: linux-ia64@vger.kernel.org
Subject: [PATCH] Fix gcc 4 warnings on ia64
Date: Tue, 16 Aug 2005 15:57:47 +0000 [thread overview]
Message-ID: <20050816155747.GN20749@wotan.suse.de> (raw)
I was compiling an IA64 2.6.13rc6 kernel on a machine with gcc 4
to test something. The compile spew a incredibly large number
of warnings. This patch fixes the most annoying ones from
commonly included makefiles. In these two cases gcc was complaining
that functions cannot be volatile or const.
There are a lot more warnings left, but they're in individual files.
Most seem to be uninitialized variables because gcc 4 can track
individual structure members for that now.
Signed-off-by: Andi Kleen <ak@suse.de>
diff -u linux-2.6.13rc6/include/asm-ia64/mmu.h-o linux-2.6.13rc6/include/asm-ia64/mmu.h
diff -u linux-2.6.13rc6/include/asm-ia64/io.h-o linux-2.6.13rc6/include/asm-ia64/io.h
--- linux-2.6.13rc6/include/asm-ia64/io.h-o 2005-06-17 21:48:29.000000000 +0200
+++ linux-2.6.13rc6/include/asm-ia64/io.h 2005-08-16 17:37:56.539836121 +0200
@@ -120,7 +120,7 @@
ia64_mfa();
}
-static inline const unsigned long
+static inline unsigned long
__ia64_get_io_port_base (void)
{
extern unsigned long ia64_iobase;
diff -u linux-2.6.13rc6/include/asm-ia64/mmu_context.h-o linux-2.6.13rc6/include/asm-ia64/mmu_context.h
--- linux-2.6.13rc6/include/asm-ia64/mmu_context.h-o 2005-08-16 17:33:16.000000000 +0200
+++ linux-2.6.13rc6/include/asm-ia64/mmu_context.h 2005-08-16 17:45:14.310318038 +0200
@@ -62,7 +62,7 @@
}
}
-static inline mm_context_t
+static inline unsigned long
get_mmu_context (struct mm_struct *mm)
{
unsigned long flags;
next reply other threads:[~2005-08-16 15:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-16 15:57 Andi Kleen [this message]
2005-08-16 23:04 ` [PATCH] Fix gcc 4 warnings on ia64 Peter Chubb
2005-08-16 23:34 ` Andi Kleen
2005-08-17 0:05 ` Luck, Tony
2005-08-17 0:11 ` Andi Kleen
2005-08-17 1:30 ` 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=20050816155747.GN20749@wotan.suse.de \
--to=ak@suse.de \
--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