From: Steve Tynor <tynor@atlanta.twr.com>
To: linux-ia64@vger.kernel.org
Subject: [Linux-ia64] gcc 0925+patch22 -> as warnings: WAW dependencies
Date: Thu, 05 Oct 2000 14:44:35 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590678205541@msgid-missing> (raw)
I'm using the 0925 toolchain with gcc version 2.96-ia64-000717 snap
000925 with the patch in the README to allow it to operate on my stock
glibc 2.1.3 Turbolinux install.
My program now seg faults in an as yet to be determined location (leaves
no stack and all registers are "0" according to gdb... joy). During the
compile, with "gcc -O", I got a number of the following warnings.
Should I be concerned? Would passing -xauto to "as" help? I'm not sure
what to make of the warnings; the first one seems to be worried about
the two stores through [r18] (but I don't understand what "resource
number is 45" is trying to tell me). The second, I'm not sure about
since I don't see any conflifts with r46 or r14 anywhere in the
vicinity. (though at least in that case "resource is 46" matches the
register in the flagged instruction).
DebugControls.s: Assembler messages:
DebugControls.s:1415: Warning: Use of 'mov' may violate WAW dependency 'GR%, % in 1 - 127' (impliedf) when entry is at label '.L55', specific resource number is 45
DebugControls.s:1415: Warning: Only the first path encountering the conflict is reported
DebugControls.s:1412: Warning: This is the location of the conflicting usage
DebugControls.s:1416: Warning: Use of 'addl' may violate WAW dependency 'GR%, % in 1 - 127' (impliedf) when entry is at label '.L55', specific resource number is 46
DebugControls.s:1416: Warning: Only the first path encountering the conflict is reported
DebugControls.s:1413: Warning: This is the location of the conflicting usage
.L15:
.loc 0 365 0
mov r15 = r43
adds r14 = -8, r43
mov r16 = r43
;;
adds r15 = -232, r43
mov r17 = r43
adds r16 = -96, r43
addl r18 = @ltoff(.LC1), gp
;;
ld8 r17 = [r18]
adds r18 = 16, r12
;;
st8 [r18] = r17
adds r17 = 16, r12
adds r18 = 24, r12
;; <<<<<<<<<<<<---- line 1412
addl r17 = 365, r0 <<<<<<<<<<<<---- line 1413
;;
st4 [r18] = r17 <<<<<<<<<<<<---- line 1415
ld8.acq r46 = [r14] <<<<<<<<<<<<---- line 1416
ld8 r47 = [r15]
ld8 r48 = [r16]
addl r14 = @ltoff(CC_com_twr_Debug#), gp
;;
Thanks,
Steve
next reply other threads:[~2000-10-05 14:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-10-05 14:44 Steve Tynor [this message]
2000-10-05 18:06 ` [Linux-ia64] gcc 0925+patch22 -> as warnings: WAW dependencies Jim Wilson
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-105590678205541@msgid-missing \
--to=tynor@atlanta.twr.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