From: Joel Soete <soete.joel@tiscali.be>
To: LKML <linux-kernel@vger.kernel.org>
Subject: [Fwd: [parisc-linux] linux and gcc 3.x question?]
Date: Sun, 06 Jun 2004 20:07:55 +0000 [thread overview]
Message-ID: <40C3799B.6000105@tiscali.be> (raw)
-------- Original Message --------
Subject: [parisc-linux] linux and gcc 3.x question?
Date: Thu, 3 Jun 2004 17:17:01 +0200
From: Joel Soete <soete.joel@tiscali.be>
To: parisc-linux@parisc-linux.org
Hello all,
I just noticed this harmless detail when I pre-compile some ncr53c8xx.c with gcc-3.3.4 on
my parisc-linux box as follow:
"gcc -Wp,-MD,drivers/scsi/.zalon53c720.o.d -nostdinc -iwithprefix include
-D__KERNEL__ -Iinclude -Wall -Wstrict-prototypes -Wno-trigraphs -fno-strict-aliasing
-fno-common -pipe -mno-space-regs -mfast-indirect-calls -mdisable-fpregs
-ffunction-sections -O2
-DCONFIG_NCR53C8XX_PREFETCH -DSCSI_NCR_BIG_ENDIAN -DCONFIG_SCSI_NCR53C8XX_NO_WORD_TRANSFERS
-DKBUILD_BASENAME=ncr53c8xx -DKBUILD_MODNAME=zalon7xx -E -o drivers/scsi/ncr53c8xx.o
drivers/scsi/ncr53c8xx.c"
I got (in drivers/scsi/ncr53c8xx.o):
[...]
static __inline__ __attribute__((always_inline)) __attribute__((always_inline))
int __attribute__((deprecated)) check_region(unsigned long s, unsigned long
n)
[...]
(2 time __attribute__((always_inline))?)
It comes from:
include/linux/compiler-gcc3.h
[...]
#if __GNUC_MINOR__ >= 1 && __GNUC_MINOR__ < 4
# define inline __inline__ __attribute__((always_inline))
# define __inline__ __inline__ __attribute__((always_inline))
# define __inline __inline__ __attribute__((always_inline))
#endif
[...]
because when I comment the second "define", I got better:
[...]
static __inline__ __attribute__((always_inline)) int __attribute__((deprecated))
check_region(unsigned long s, unsigned long n)
[...]
I very doubt that's the right thing to do so if somebody as any idea?
TIA,
Joel
PS: please make me in cc (I am not in this list)
reply other threads:[~2004-06-06 20:07 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=40C3799B.6000105@tiscali.be \
--to=soete.joel@tiscali.be \
--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.