search for: enflame

Displaying 4 results from an estimated 4 matches for "enflame".

2018 Nov 15
2
Per-write cycle count with ReadAdvance - Do I really need that?
...ny existed method to meet my requirement. Anyway the latencies here seems to be decided by considering both a) 3 kinds of Write, b) 2 kinds of Read. Therefore I doubt if it can not be modeled with current tblgen implement. Can you comment and help? -- Garfee Guan, LLVM Compiler Backend Engineer Enflame Technology Co. Website: http://www.enflame-tech.com/ -------------------------------------------------------------------- [llvm-dev] Per-write cycle count with ReadAdvance *Pierre-Andre Saulais via llvm-dev* llvm-dev at lists.llvm.org <llvm-dev%40lists.llvm.org?Subject=Re%3A%20%5Bllvm-dev%5D%20...
2018 Nov 17
2
Per-write cycle count with ReadAdvance - Do I really need that?
...would have any effect > at all: > > // Forward from a vector op (normal, add, mul) to a store. > def : ReadAdvance<MyReadStoreVector, 0, > [WriteVector, MyWriteAddVector, MyWriteMulVector]>; > > -Andy > > -- > Garfee Guan, > LLVM Compiler Backend Engineer > Enflame Technology Co. > Website: http://www.enflame-tech.com/ > > -------------------------------------------------------------------- > [llvm-dev] Per-write cycle count with ReadAdvance > *Pierre-Andre Saulais via llvm-dev* llvm-dev at lists.llvm.org > <llvm-dev%40lists.llvm.org?Subj...
2018 Nov 19
2
Per-write cycle count with ReadAdvance - Do I really need that?
...>> // Forward from a vector op (normal, add, mul) to a store. >> def : ReadAdvance<MyReadStoreVector, 0, >> [WriteVector, MyWriteAddVector, MyWriteMulVector]>; >> >> -Andy >> >> -- >> Garfee Guan, >> LLVM Compiler Backend Engineer >> Enflame Technology Co. >> Website: http://www.enflame-tech.com/ >> >> -------------------------------------------------------------------- >> [llvm-dev] Per-write cycle count with ReadAdvance >> *Pierre-Andre Saulais via llvm-dev* llvm-dev at lists.llvm.org >> <llvm-d...
2006 Aug 03
31
CentOS Based Fierwall Document
For those of you that either have an older revision of my firewall document, or are otherwise keeping track of it, there is a new version available. The current version of the document is version 3.1. It's changed rather significantly in some areas.