search for: rerolls

Displaying 20 results from an estimated 25 matches for "rerolls".

Did you mean: reroll
2015 Jun 03
3
[LLVMdev] Replacing a repetitive sequence of code with a loop
On 3 June 2015 at 19:57, Benjamin Kramer <benny.kra at gmail.com> wrote: > There's a loop reroll pass in LLVM trunk that should do exactly this transformation. Though that's a loop pass (runOnLoop). What you could do is add a previous pass that would recognize the pattern and create a loop of 1 iteration around the code and then run the reroll pass. If your pattern recognition
2007 Dec 10
1
Rerolling k-means
Hi all I am working on k-means algorithm (in R: kmeans( ) ). The R-help advice us to try several random start in order to avoid local minimum. Does one know if there is a procedure that automaticly run this rerolling and select the best partition ? Or any studies that gives clues on the number of rerolling ? Thanks for helping. Christophe
2013 Oct 23
0
[LLVMdev] [PATCH] Loop Rerolling Pass
I mistakenly not cc’ed the list. On Oct 23, 2013, at 8:28 AM, Renato Golin <renato.golin at linaro.org> wrote: > On 23 October 2013 14:13, Arnold <aschwaighofer at apple.com> wrote: >> What I am proposing for interleaved data vectorization would not transform the loop before vectorization (because there is not much you can do in the general case). There would not be a need
2004 Feb 18
0
cvs commit: ports/devel/tmake Makefile distinfo
On Tue, Feb 17, 2004 at 02:20:46PM +0100, Michael Nottebrock wrote: [distfile rerolls] > I didn't know that I was supposed to perform a security audit and I did not do > so. So if anyone happens to have the old distfile still around, please send > it my way, cause I don't. I suggest next time instead of marking a port as > BROKEN= Checksum mismatch, mark it as...
2015 Jun 03
2
[LLVMdev] Replacing a repetitive sequence of code with a loop
Hey guys, in an HPC project I am working on I am given an LLVM program consisting of a linear sequence of repetitive junks of code with an uniform memory access pattern. Each code junk does the following: 1) loads some memory, 2) performs some arithmetic operations, 3) stores the result back to memory. The memory stride between consecutive junks is constant over the whole program, thus the
2016 Nov 24
2
Implementing secondary quota w/ "Archive" namespace
On 24 Nov 2016, at 9.33, Mark Moseley <moseleymark at gmail.com> wrote: > > On Wed, Nov 23, 2016 at 6:05 PM, Timo Sirainen <tss at iki.fi> wrote: > >> On 23 Nov 2016, at 0.49, Mark Moseley <moseleymark at gmail.com> wrote: >>> >>> If I move messages between namespaces, it appears to ignore the quotas >> I've >>> set on them.
2016 Nov 24
2
Implementing secondary quota w/ "Archive" namespace
On 23 Nov 2016, at 0.49, Mark Moseley <moseleymark at gmail.com> wrote: > > If I move messages between namespaces, it appears to ignore the quotas I've > set on them. A *copy* will trigger the quota error. But a *move* just > happily piles on to the overquota namespace. Is that normal? Probably needs a bit more thinking, but I guess the attached patch would help.
2012 Feb 09
0
[LLVMdev] Vectorization: Next Steps
On Feb 7, 2012, at 12:10 PM, Hal Finkel wrote: >>> 1. "Target Data" for vectorization - I think that in order to improve >>> the vectorization quality, the vectorizer will need more information >>> about the target. This information could be provided in the form of a >>> kind of extended target data. This extended target data might contain:
2012 Feb 09
1
[LLVMdev] Vectorization: Next Steps
On Wed, 2012-02-08 at 17:26 -0800, Chris Lattner wrote: > On Feb 7, 2012, at 12:10 PM, Hal Finkel wrote: > >>> 1. "Target Data" for vectorization - I think that in order to improve > >>> the vectorization quality, the vectorizer will need more information > >>> about the target. This information could be provided in the form of a > >>>
2012 Feb 07
4
[LLVMdev] Vectorization: Next Steps
On Mon, 2012-02-06 at 14:26 -0800, Chris Lattner wrote: > On Feb 2, 2012, at 7:56 PM, Hal Finkel wrote: > > As some of you may know, I committed my basic-block autovectorization > > pass a few days ago. I encourage anyone interested to try it out (pass > > -vectorize to opt or -mllvm -vectorize to clang) and provide feedback. > > Especially in combination with
2014 Apr 08
9
[LLVMdev] 3.4.1 Release Plans
Tom (and Andy, Owen, Evan, Nadav), I'd like the following commits placed into the 3.4.1 branch. I've attempted to sort this list by code owner: Andrew Trick: r203719 - PR17473 r203725 - This test need the X86 backend, move it to the X86 sub directory. [adjusts the test location from r203719] r202273 - Fix PR18165: LSR must avoid scaling factors that exceed the limit on truncated use.
2000 Aug 28
3
optimization patches
Well, here you are. 24k; sorry if I'm not supposed to put this size things in your mailbox, didn't know where else to put it. And you all are subscribed to vorbis-dev, after all. I'm not that good at breaking patches apart, so it's one big patch. Sorry. Overview: configure.in make profiling easier & more useful decoder-example.c (#if 0'ed) dither output;
2015 Dec 17
2
RFC: Hotness thresholds in profile header
On Thu, Dec 17, 2015 at 9:21 AM, Andy Ayers <andya at microsoft.com> wrote: > While your bb count distribution is extremely likely to be some kind of power-law like distribution, it's not guaranteed. > > Also you might think about operations that can amplify (rerolling) or appear to amplify (TRE) or diminish BB counts, and how you'd go about reclassifying block hotness. yes
2016 Nov 24
0
Implementing secondary quota w/ "Archive" namespace
On Wed, Nov 23, 2016 at 6:05 PM, Timo Sirainen <tss at iki.fi> wrote: > On 23 Nov 2016, at 0.49, Mark Moseley <moseleymark at gmail.com> wrote: > > > > If I move messages between namespaces, it appears to ignore the quotas > I've > > set on them. A *copy* will trigger the quota error. But a *move* just > > happily piles on to the overquota namespace.
2016 Nov 25
0
Implementing secondary quota w/ "Archive" namespace
On Thu, Nov 24, 2016 at 10:52 AM, Timo Sirainen <tss at iki.fi> wrote: > On 24 Nov 2016, at 9.33, Mark Moseley <moseleymark at gmail.com> wrote: > > > > On Wed, Nov 23, 2016 at 6:05 PM, Timo Sirainen <tss at iki.fi> wrote: > > > >> On 23 Nov 2016, at 0.49, Mark Moseley <moseleymark at gmail.com> wrote: > >>> > >>> If I
2008 Feb 11
5
local root exploit
I saw that there is a local root exploit in the wild. http://blog.kagesenshi.org/2008/02/local-root-exploit-on-wild.html And I see my centos box still has: 2.6.18-53.1.4.el5 yum says there are no updates... am I safe? Valent.
2016 Dec 01
2
Implementing secondary quota w/ "Archive" namespace
On Thu, Nov 24, 2016 at 9:10 PM, Mark Moseley <moseleymark at gmail.com> wrote: > On Thu, Nov 24, 2016 at 10:52 AM, Timo Sirainen <tss at iki.fi> wrote: > >> On 24 Nov 2016, at 9.33, Mark Moseley <moseleymark at gmail.com> wrote: >> > >> > On Wed, Nov 23, 2016 at 6:05 PM, Timo Sirainen <tss at iki.fi> wrote: >> > >> >> On
2015 Dec 17
2
RFC: Hotness thresholds in profile header
On Wed, Dec 16, 2015 at 6:00 PM, Andy Ayers <andya at microsoft.com> wrote: > I’ve done similar rankings with profile data and found it worked out pretty > well. > > > > In my case it was ranking function hotness but the idea was similar: sort by > weight, compute various percentile cutoff points, and use those to classify. > I put in some compensation for truly
2012 Feb 13
1
[LLVMdev] Vectorization: Next Steps
On Wed, 2012-02-08 at 17:26 -0800, Chris Lattner wrote: > On Feb 7, 2012, at 12:10 PM, Hal Finkel wrote: > >>> 1. "Target Data" for vectorization - I think that in order to improve > >>> the vectorization quality, the vectorizer will need more information > >>> about the target. This information could be provided in the form of a > >>>
2008 Aug 12
4
NFS issues
So I'm running nfs to get content to my web servers. Now I've had this problem 2 times (about 2 weeks since the last occurrence). I use drbd on the nfs server for redundancy. Now to my problem: All my web sites stopped responding so I started by checking dmesg and there I found a bunch of this errors || Aug 11 16:00:39 web03 kernel: lockd: server 192.168.20.22 not responding, timed out