public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: "Neelakantam, NaveenX" <naveenx.neelakantam@intel.com>
To: linux-ia64@vger.kernel.org
Subject: RE: [Linux-ia64] determining read or write on a page fault
Date: Tue, 16 Apr 2002 20:18:15 +0000	[thread overview]
Message-ID: <marc-linux-ia64-105590701905458@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590701905163@msgid-missing>

Yes, I meant gcc (version 2.96 20000731).  I've verified that the bug still
exists in gcc3.0, but I haven't been able to create a testcase yet.

Naveen

-----Original Message-----
From: David Mosberger [mailto:davidm@napali.hpl.hp.com]
Sent: Monday, April 15, 2002 11:55 AM
To: Neelakantam, NaveenX
Cc: Hoeflinger, Jay P; 'davidm@hpl.hp.com'; 'linux-ia64@linuxia64.org'
Subject: RE: [Linux-ia64] determining read or write on a page fault


>>>>> On Sun, 14 Apr 2002 15:08:54 -0700, "Neelakantam, NaveenX"
<naveenx.neelakantam@intel.com> said:

  Naveen> It turns out that we have been running into a cc code
  Naveen> generation bug.  Changing the si_code = 0 case from "write"
  Naveen> to "read" happened to make the bug go away.

  Naveen> We have rewritten our code to workaround the bug, and
  Naveen> everything works as expected.  Sorry for the false alarm.

By "cc" do you mean gcc?  If so, what version?  Can you check whether
the bug still occurs with the latest version of gcc (gcc3.0 or, better
still, gcc3.1-prelease) or provide a test-case?

Thanks,

	--david


      parent reply	other threads:[~2002-04-16 20:18 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-21 21:09 [Linux-ia64] determining read or write on a page fault Hoeflinger, Jay P
2002-02-21 21:57 ` Boehm, Hans
2002-02-22 15:58 ` Hoeflinger, Jay P
2002-02-22 17:06 ` David Mosberger
2002-02-22 17:27 ` Hoeflinger, Jay P
2002-02-22 17:29 ` n0ano
2002-02-22 18:45 ` David Mosberger
2002-02-23  1:24 ` David Mosberger
2002-02-25 17:07 ` Hoeflinger, Jay P
2002-02-25 18:36 ` David Mosberger
2002-04-03 16:18 ` Hoeflinger, Jay P
2002-04-04 21:59 ` David Mosberger
2002-04-04 22:49 ` Neelakantam, NaveenX
2002-04-14 22:08 ` Neelakantam, NaveenX
2002-04-15 16:55 ` David Mosberger
2002-04-16 20:18 ` Neelakantam, NaveenX [this message]

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-105590701905458@msgid-missing \
    --to=naveenx.neelakantam@intel.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