Displaying 2 results from an estimated 2 matches for "stackprotectorcheck".
2015 Dec 01
10
[RFC] Intrinsic naming convention (words with dots)
...tchpoint
@llvm.experimental.gc.statepoint
@llvm.returnaddress
@llvm.frameaddress
@llvm.localescape
@llvm.localrecover
@llvm.stacksave
@llvm.stackrestore
@llvm.pcmarker
@llvm.readcyclecounter
@llvm.bitreverse
@llvm.eh.begincatch
@llvm.eh.endcatch
@llvm.eh.padparam
@llvm.stackprotector
@llvm.stackprotectorcheck
@llvm.objectsize
@llvm.donothing
Words with dots:
@llvm.sadd.with.overflow
@llvm.uadd.with.overflow
@llvm.ssub.with.overflow
@llvm.usub.with.overflow
@llvm.smul.with.overflow
@llvm.umul.with.overflow
@llvm.convert.to.fp16
@llvm.convert.from.fp16
@llvm.eh.typeid.for
@llvm.init.trampoline
@llvm...
2016 Mar 26
0
[SSP] Simplifying SSP code paths
...ent code paths. I wonder if we
can at least have only two code paths, one for SelectionDAG and the other
for FastISel.
IR pass may generate two forms of IR:
1) Almost pure IR, which contains only llvm.stackprotector that can be
lowered.
2) An IR skeleton which contains llvm.stackprotector and
llvm.stackprotectorcheck.
FastISel only needs to look at 1). However, if FastISel fails to lower it
(which is certainly possible), it falls back to SelectionDAG. SelectionDAG
must handle 1) form. SelectionDAG must handle 2) form, since it's only for
SelectionDAG.
*Conclusion 1*: if FastISel is able to fallback to Sel...