From: Steffen Persvold <sp@scali.com>
To: linux-ia64@vger.kernel.org
Subject: [Linux-ia64] Compiler warnings.
Date: Sat, 22 Jun 2002 09:53:40 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590701905704@msgid-missing> (raw)
Hi all,
For some time I've been compiling applications and kernels on IA64.
Sometimes the assembler gives me warnings about "RAW dependencies" which
makes me wonder about the quality of the gcc compiler. Is this something
that should be paid attention to ?
Here's a warning (and not the only one) I get when I compile the latest
2.4.18 patchset with gcc 2.96 (gcc version 2.96 20000731 (Debian GNU/Linux
IA64 experimental)) :
gcc -D__KERNEL__ -I/usr/src/linux-2.4.18-020622/include
-Wall -Wstrict-prototypes -Wno-trigraphs -g -O2 -fomit-frame-pointer
-fno-strict-aliasing -fno-common -pipe -ffixed-r13
-mfixed-rangeñ0-f15,f32-f127 -falign-functions2 -mconstant-gp
-DKBUILD_BASENAME=vmscan -c -o vmscan.o vmscan.c
{standard input}: Assembler messages:
{standard input}:594: Warning: Use of 'st8' violates RAW dependency 'DTC' (data)
{standard input}:594: Warning: Only the first path encountering the conflict is reported
{standard input}:581: Warning: This is the location of the conflicting usage
I haven't tried the 3.0.1 compiler yet.
Thanks,
--
Steffen Persvold | Scalable Linux Systems | Try out the world's best
mailto:sp@scali.com | http://www.scali.com | performing MPI implementation:
Tel: (+47) 2262 8950 | Olaf Helsets vei 6 | - ScaMPI 1.13.8 -
Fax: (+47) 2262 8951 | N0621 Oslo, NORWAY | >320MBytes/s and <4uS latency
next reply other threads:[~2002-06-22 9:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-22 9:53 Steffen Persvold [this message]
2002-06-22 9:58 ` [Linux-ia64] Compiler warnings Steffen Persvold
2002-06-22 19:11 ` 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-105590701905704@msgid-missing \
--to=sp@scali.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