From: CH Gowri Kumar <gkumar@csa.iisc.ernet.in>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] [hinkelbein@ti.uni-mannheim.de: Re: Strange problems
Date: Mon, 19 May 2003 14:33:06 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590723705943@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590723705942@msgid-missing>
Comments inline.
> .file "waw.c"
> .pred.safe_across_calls p1-p5,p16-p63
> .text
> .align 16
> .global f#
> .proc f#
> f:
> .prologue
> .body
> .mii
> addl r3 = @ltoff(sh#), gp
> cmp4.eq p8, p9 = 0, r32
> ;;
> nop.i 0
> .mmi
> ld8 r2 = [r3]
> ;;
> ld4 r14 = [r2]
> nop.i 0
> ;;
> .mii
> (p9) cmp4.eq p6, p7 = 1, r14 ! it is this stuff that triggers the
> asm warning.
> (p8) cmp4.eq p6, p7 = 2, r14 !
> ;; !
> (p6) mov r8 = r0 !
> .mib !
> (p7) addl r8 = 13, r0 !
It is at this place the assembler is cribbing.
There are two statements which are writing to the same register ofcourse
with appropriate predicate registers.
(p6) mov r8 = r0
(p7) addl r8 = r13,r0
But the predicate register p6 and p7 are set by the just above statements
> (p9) cmp4.eq p6, p7 = 1, r14
> (p8) cmp4.eq p6, p7 = 2, r14
which are again dependent on the predicates p8 and p9 which are set by the
statment:
> cmp4.eq p8, p9 = 0, r32
I feel that the assembler is not able to recognize that the two statements
which are writing to the same register(r8) are mutually exclusive ( only
one of them can be executed), as it is two levels dependant on predicate
registers.
Anyway, it's just a warning, not an error.
Regards,
Gowri Kumar
next prev parent reply other threads:[~2003-05-19 14:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-19 13:36 [Linux-ia64] [hinkelbein@ti.uni-mannheim.de: Re: Strange problems building bigloo on ia64] Matthew Wilcox
2003-05-19 14:33 ` CH Gowri Kumar [this message]
2003-05-19 16:27 ` Keith Owens
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-105590723705943@msgid-missing \
--to=gkumar@csa.iisc.ernet.in \
--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 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.