[llvm-bugs] [Bug 28061] New: UpdateCompilerUsed should handle __stack_chk_guard

[via llvm-bugs]

https://llvm.org/bugs/show_bug.cgi?id=28061

            Bug ID: 28061
           Summary: UpdateCompilerUsed should handle __stack_chk_guard
           Product: libraries
           Version: trunk
          Hardware: PC
                OS: All
            Status: NEW
          Severity: normal
          Priority: P
         Component: Interprocedural Optimizations
          Assignee: unassignedbugs at nondot.org
          Reporter: rafael.espindola at gmail.com
                CC: llvm-bugs at lists.llvm.org
    Classification: Unclassified

Currently UpdateCompilerUsed handles functions that the backend can introduce
references to.  They are added to llvm.compiler_used.

For example, if we pass llvm-lto this input

define void @memcpy() {
  ret void
}

the output will have

@llvm.compiler.used = appending global [1 x i8*] [i8* bitcast (i8* (i8*, i8*,
i64)* @memcpy to i8*)], section "llvm.metadata"

It should do the same for variables the backend can introduce an use.
__stack_chk_guard is one such variable, but there may be others.

With this in place we can then delete the hard coded handling of
__stack_chk_guard in internalize.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-bugs/attachments/20160609/13dba87d/attachment.html>