From: "Mike Black" <mblack@csihq.com>
To: "linux-kernel" <linux-kernel@vger.kernel.org>
Subject: 2.4.16 Compiler warning
Date: Wed, 28 Nov 2001 05:48:28 -0500 [thread overview]
Message-ID: <000701c177fa$36872380$e1de11cc@csihq.com> (raw)
This appears to be a non-fatal warning....does this need to be cleaned up?
gcc 2.95.3
gcc -D__KERNEL__ -I/usr/src/linux/include -Wall -Wstrict-prototypes -Wno-tri
graphs -O2 -fomit-frame-pointer -fno-strict-aliasing -fn
o-common -pipe -mpreferred-stack-boundary=2 -march=i686 -c -o pci-pc.o
pci-pc.c
{standard input}: Assembler messages:
{standard input}:1107: Warning: indirect lcall without `*'
{standard input}:1192: Warning: indirect lcall without `*'
{standard input}:1279: Warning: indirect lcall without `*'
{standard input}:1361: Warning: indirect lcall without `*'
{standard input}:1372: Warning: indirect lcall without `*'
{standard input}:1383: Warning: indirect lcall without `*'
{standard input}:1470: Warning: indirect lcall without `*'
{standard input}:1482: Warning: indirect lcall without `*'
{standard input}:1494: Warning: indirect lcall without `*'
{standard input}:1975: Warning: indirect lcall without `*'
{standard input}:2068: Warning: indirect lcall without `*'
Here's all the lcall's in pci-pc.c:
__asm__("lcall (%%edi); cld"
"lcall (%%edi); cld\n\t"
__asm__("lcall (%%edi); cld\n\t"
__asm__("lcall (%%esi); cld\n\t"
__asm__("lcall (%%esi); cld\n\t"
__asm__("lcall (%%esi); cld\n\t"
__asm__("lcall (%%esi); cld\n\t"
__asm__("lcall (%%esi); cld\n\t"
__asm__("lcall (%%esi); cld\n\t"
"lcall (%%esi); cld\n\t"
__asm__("lcall (%%esi); cld\n\t"
________________________________________
Michael D. Black Principal Engineer
mblack@csihq.com 321-676-2923,x203
http://www.csihq.com Computer Science Innovations
http://www.csihq.com/~mike My home page
FAX 321-676-2355
next reply other threads:[~2001-11-28 10:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-28 10:48 Mike Black [this message]
2001-11-28 15:19 ` 2.4.16 Compiler warning Kai Germaschewski
-- strict thread matches above, loose matches on Subject: below --
2001-11-28 21:58 Mikael Pettersson
2001-11-28 22:14 ` [MOc]cda*mirabilos
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='000701c177fa$36872380$e1de11cc@csihq.com' \
--to=mblack@csihq.com \
--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.