[LLVMbugs] [Bug 4135] New: PointerMayBeCaptured() vs. readonly/readnone

bugzilla-daemon at cs.uiuc.edu bugzilla-daemon at cs.uiuc.edu
Sun May 3 04:43:02 PDT 2009


           Summary: PointerMayBeCaptured() vs. readonly/readnone
           Product: new-bugs
           Version: unspecified
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: new bugs
        AssignedTo: unassignedbugs at nondot.org
        ReportedBy: fvbommel at wxs.nl
                CC: llvmbugs at cs.uiuc.edu

PointerMayBeCaptured (in Analysis/CaptureTracking) assumes that
readonly/readnone functions returning void can't capture their pointer
arguments. Due to the "visible to caller functions" clauses in the attribute
definitions this isn't technically correct.

(If this is resolved by changing the attribute descriptions to remove those
clauses, please also update PointerMayBeCaptured to handle readonly/readnone
functions returning pointers by tracking the return value)

Configure bugmail: http://llvm.org/bugs/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.

More information about the llvm-bugs mailing list