public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: David Mosberger <davidm@napali.hpl.hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [PATCH] new ".serialize" gas directive
Date: Mon, 10 May 2004 20:16:33 +0000	[thread overview]
Message-ID: <16543.58145.776571.385405@napali.hpl.hp.com> (raw)
In-Reply-To: <16537.51724.854691.934006@napali.hpl.hp.com>

>>>>> On 07 May 2004 00:48:46 -0700, Jim Wilson <wilson@specifixinc.com> said:

  Jim> I don't have a lot of time for IA-64 gcc work at the moment.  It might
  Jim> be useful to have a gcc bug report for this so we don't lose track of
  Jim> it.

I was going to submit a bug-report, but it's difficult to provide a
reliable test-case, because other changes in the compiler can easily
make one particular warning go away, just to show up in some other
place.  For example, with the CVS gcc (pre-3.5), the warning from
mm/vmscan.c is gone but instead we get several other warnings such as
this one from net/drivers/bonding/bond_main.c:

$ as -x drivers/net/bonding/bond_main.s
drivers/net/bonding/bond_main.s: Assembler messages:
drivers/net/bonding/bond_main.s:3409: Warning: Use of 'addl' may violate WAW dependency 'GR%, % in 1 - 127' (impliedf), specific resource number is 42
drivers/net/bonding/bond_main.s:3408: Warning: This is the location of the conflicting usage

The code in question looks like this:

	cmp4.eq p12, p13 = 6, r14
	addl r28 = @ltoffx(.LC26), r1
	mov r40 = r32 ;;

  (p13) cmp.eq p16, p17 = 0, r34
	ld8.mov r41 = [r28], .LC26
  (p12) br.cond.dpnt .L1108 ;;

  (p16) addl r42 = @ltoffx(.LC28), r1
  (p17) addl r42 = @ltoffx(.LC27), r1

So, I think the best the bug report could say is "try building the
Linux kernel and look for spurious dependency-violation warnings".  Is
this worth putting in a bug-report?

	--david

  parent reply	other threads:[~2004-05-10 20:16 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-06  5:15 [PATCH] new ".serialize" gas directive David Mosberger
2004-05-06 23:33 ` Jim Wilson
2004-05-06 23:47 ` David Mosberger
2004-05-07  7:48 ` Jim Wilson
2004-05-10 20:16 ` David Mosberger [this message]
2004-05-14  8:43 ` Jim Wilson
2004-05-14 18:30 ` David Mosberger
2004-06-16  1:54 ` Chris Wedgwood
2004-06-16 21:57 ` Jim Wilson
2004-06-16 22:04 ` Chris Wedgwood
2004-06-16 22:42 ` Jim Wilson
2004-06-16 22:56 ` Luck, Tony
2004-06-16 23:01 ` 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=16543.58145.776571.385405@napali.hpl.hp.com \
    --to=davidm@napali.hpl.hp.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