search for: discrimin

...#39;s sample count). When loading this profile into compiler, it will think the loop trip count is 2 instead of 8. Proposal: When compiler duplicates code, it encodes the duplication info in the debug info. As the duplication is not interesting to debugger, I propose to encode this as part of the discriminator. There are 2 types of code duplication: 1. duplicated code are guaranteed to have the same execution count (e.g. loop unroll and loop vectorize). We can record the duplication factor, for the above example "4" is recorded in the discriminator. 2. duplicated code that may have differ...

...optimizations, we use a helper pass to recompute the flow sensitive profile just before this pass. When loading this profile, we will recompute the branch probability and hopefully improve the optimization quality for that target pass. The flow sensitivity in the profile is through a hierarchical discriminator scheme that can better preserve flow information in the Perf profile. 2.1. Current Use of Discriminators The AFDO profile contains a discriminator field whose goal is to differentiate statements with the same line number in the source code (largely from MACRO expansions). Discriminators wer...

...compiler, it will think the loop trip >> count is 2 instead of 8. >> >> Proposal: >> When compiler duplicates code, it encodes the duplication info in the >> debug info. As the duplication is not interesting to debugger, I propose to >> encode this as part of the discriminator. >> >> There are 2 types of code duplication: >> >> 1. duplicated code are guaranteed to have the same execution count (e.g. >> loop unroll and loop vectorize). We can record the duplication factor, for >> the above example "4" is recorded in the di...

...ading this profile into compiler, it will think the loop trip count > is 2 instead of 8. > > Proposal: > When compiler duplicates code, it encodes the duplication info in the > debug info. As the duplication is not interesting to debugger, I propose to > encode this as part of the discriminator. > > There are 2 types of code duplication: > > 1. duplicated code are guaranteed to have the same execution count (e.g. > loop unroll and loop vectorize). We can record the duplication factor, for > the above example "4" is recorded in the discriminator. > 2. dup...

...ading this profile into compiler, it will think the loop trip count > is 2 instead of 8. > > Proposal: > When compiler duplicates code, it encodes the duplication info in the > debug info. As the duplication is not interesting to debugger, I propose to > encode this as part of the discriminator. > > There are 2 types of code duplication: > > 1. duplicated code are guaranteed to have the same execution count (e.g. > loop unroll and loop vectorize). We can record the duplication factor, for > the above example "4" is recorded in the discriminator. > 2. dup...

Hello everyone, I am totally new to the R program. I have had a look at some pdf documents that I downloaded and that explain how to do many things in R; however, I still cannot figure out how to do what I want to do, which is to perform Discriminant Correspondence Analysis on a rectangular matrix of data that I have in an Excel file. I know R users frown upon Excel and recommend converting Excel files to .csv format, which I have done, no problem. That is not an issue. There are several parts to my problem. 1) When I try the read.table comm...

...the loop trip >>> count is 2 instead of 8. >>> >>> Proposal: >>> When compiler duplicates code, it encodes the duplication info in the >>> debug info. As the duplication is not interesting to debugger, I propose to >>> encode this as part of the discriminator. >>> >>> There are 2 types of code duplication: >>> >>> 1. duplicated code are guaranteed to have the same execution count (e.g. >>> loop unroll and loop vectorize). We can record the duplication factor, for >>> the above example "4&quo...

...ture, I suspect we'll end up with transformations that produce even more versions of loops (Intel's compiler, for example, has a useful pragma that allows the user to request loop specializations for a specified set of trip counts). I'd like to have a scheme where the source location + discriminator can be mapped to information about the relevant loop version so that our profiling tools can display that information usefully to the user, and so that our optimizations can make useful choices (i.e. don't bother vectorizing a loop when the scalar loop is run a lot but the vectorized versio...

...ly, can users upgrade compiler with FS-AutoFDO support but without refreshing their profile? I think it's important to make new improvement like this as opt-in, so other users of AutoFDO can choose if and when they want to make the switch from AutoFDO to FS-AutoFDO. With the proposed changes to discriminator encoding, sounds like we are going to eliminate duplication factor etc. altogether. In that case, multiple FS-AutoFDO sample profile loading would be required in order to not regress from today's AutoFDO due to lack of duplication factor. Is that correct? If so, this change as is can break...

It looks like the example doesn't use the encoding described in the text? Assume that the discriminator is uint32. The traditional discriminator is less than 256, let's take 8 bit for it. For duplication factor (type 1 duplication), we assume the maximum unroll_factor * vectorize_factor is less than 256, thus 8 bit for it. For unique number(type 2 duplication), we assume code is at most dupli...

...Hal Finkel" <hfinkel at anl.gov> > Cc: "Xinliang David Li" <davidxl at google.com>, "llvm-dev" > <llvm-dev at lists.llvm.org> > Sent: Tuesday, November 1, 2016 11:43:41 AM > Subject: Re: [llvm-dev] (RFC) Encoding code duplication factor in > discriminator > On Fri, Oct 28, 2016 at 3:07 PM, Hal Finkel < hfinkel at anl.gov > > wrote: > > Hi Dehao, > > > This is definitely an important problem, thanks for writing this > > up! > > > There is a related problem that I think we can address at the same &gt...

...;Hal Finkel" <hfinkel at anl.gov> > Cc: "llvm-dev" <llvm-dev at lists.llvm.org>, "Xinliang David Li" > <davidxl at google.com> > Sent: Tuesday, November 1, 2016 8:24:30 PM > Subject: Re: [llvm-dev] (RFC) Encoding code duplication factor in > discriminator > On Tue, Nov 1, 2016 at 5:56 PM, Hal Finkel < hfinkel at anl.gov > wrote: > > > From: "Dehao Chen" < dehao at google.com > > > > > > > To: "Hal Finkel" < hfinkel at anl.gov > > > > > > > Cc: "llvm-...

Dear All This is more of a statistics question than a question about help for R, so forgive me. I am using lda from the MASS package to perform linear discriminant function analysis. I have 14 cases belonging to two groups and have measured each of 37 variables. I want to find those variables that best discriminate between the two groups, and I want to visualise that and create a classification function. Please note at this stage it is a proof of concep...

...als of this RFC), profile should only reflect the attribute of source, not compiler transformations. But there are sample pgo users who does *not* care about iterative sample pgo performance, for them, as Hal suggested, we should invent a more extensible way to preserve profile context. Apparently discriminator is not an extensible choice. So how about we just use discriminator to store the attribute of the source (i.e trip count), and later design new extensible ways in dwarf to represent more context info? Adrian also suggested that we may need to consider have a flag or a separate debugging mode t...

...bution is inherently ambiguous. In those cases, I have no problem with Just Doing It. Something likely to pad the line table to benefit profiling without similarly benefiting debugging… that's probably worth inventing a –gprofile or some such. I suspect Dehao's more elaborate ideas about discriminators fall into that category (although IIRC discriminators were invented mainly to benefit profiling in the first place, so maybe having discriminators at all would be something to put under a –gprofile kind of option). --paulr From: David Blaikie [mailto:dblaikie at gmail.com] Sent: Monday, Novem...

...;Hal Finkel" <hfinkel at anl.gov> > Cc: "Xinliang David Li" <davidxl at google.com>, "llvm-dev" > <llvm-dev at lists.llvm.org> > Sent: Tuesday, November 1, 2016 1:24:01 PM > Subject: Re: [llvm-dev] (RFC) Encoding code duplication factor in > discriminator > On Tue, Nov 1, 2016 at 10:50 AM, Hal Finkel < hfinkel at anl.gov > > wrote: > > > From: "Dehao Chen" < dehao at google.com > > > > > > > To: "Hal Finkel" < hfinkel at anl.gov > > > > > > > Cc: &quot...

Hi everyone, I'm trying to solve a problem about how to get the Fisher's discriminant functions of a "lda" (linear discriminant analysis) object, I mean, the object obtained from doing "lda(formula, data)" function of the package MASS in R-project. This object gives me the canonical linear functions (n-1 coefficients matrix of n groups at least), and only with...

...l expose compiler implementation detail in debug info. This is still doable, assume we have 15 interesting optimizations to track, we can use 4 bits to encode the optimization type that created the clone. But this becomes nasty if the a clone is created by more than one optimizations. In that way, discriminator may not be fit for this purpose. My understanding was that the encoding scheme would allow the profiling analysis to correctly map execution data back to the original source construct, while preserving the property that each distinct basic block would have its own discriminator value. That is...

...;Hal Finkel" <hfinkel at anl.gov> > Cc: "llvm-dev" <llvm-dev at lists.llvm.org>, "Xinliang David Li" > <davidxl at google.com> > Sent: Tuesday, November 1, 2016 6:41:29 PM > Subject: Re: [llvm-dev] (RFC) Encoding code duplication factor in > discriminator > On Tue, Nov 1, 2016 at 2:36 PM, Hal Finkel < hfinkel at anl.gov > wrote: > > > From: "Hal Finkel via llvm-dev" < llvm-dev at lists.llvm.org > > > > > > > To: "Dehao Chen" < dehao at google.com > > > > > >...

On Jan 1, 2009, at 6:25 AM, Jon Harrop wrote: >> Exactly. I'm not especially interested in C-style unions, I'm >> interested >> in discriminated unions. But the actual discriminator field is easily >> represented in LLVM IR already, so there's no need to extend the IR >> to >> support them. That's why I am only asking for C-style union support - >> it's a lower-level primitive that you can use to bu...