First Last Prev Next    No search results available
Details
: Memory Mapped I/O Intrinsics do not fence memory
Bug#: 566
: libraries
: Backend: X86
Status: RESOLVED
Resolution: WONTFIX
: PC
: Linux
: 1.5
: P2
: minor
: ---
:
:
:
:
  Show dependency tree - Show dependency graph
People
Reporter: John T. Criswell <criswell@uiuc.edu>
Assigned To: Unassigned LLVM Bugs <unassignedbugs@nondot.org>

Attachments
Add an attachment (proposed patch, testcase, etc.)


Note

You need to log in before you can comment on or make changes to this bug.

Related actions

Description:   Opened: 2005-05-18 10:29 
According to the design in the language reference manual, the LLVM readio and
writeio intrinsics should strongly order I/O memory accesses.

However, the current implementation lowers these intrinsics to volatile loads
and stores on ix86.  These loads and stores may or may not be properly ordered,
depending on the processor on which they run.

The correct solution is not obvious.  Certain fencing instructions are not found
on older Pentium processors, and we will need a general fencing model for SMP
systems anyway.  Such a design has not been discussed, though, as far as I know.
------- Comment #1 From Chris Lattner 2006-03-02 18:17:28 ------- 
This bug is obsolete.
First Last Prev Next    No search results available