similar to: Can creating new forms of debug info metadata be simplified?

> On May 29, 2018, at 12:55, Adrian Prantl <aprantl at apple.com> wrote: > > > >> On May 29, 2018, at 12:28 PM, David Blaikie <dblaikie at gmail.com <mailto:dblaikie at gmail.com>> wrote: >> >> +some of the debug info cabal (& Duncan, as an emeritus member, and person who plumbed a lot of the current debug info syntax support in) >>

+some of the debug info cabal (& Duncan, as an emeritus member, and person who plumbed a lot of the current debug info syntax support in) Visitor seems plausible though I haven't looked at the code in detail to see if it'd work perfectly. On Tue, May 29, 2018 at 7:56 AM Sohail Somani (Fizz Buzz Inc.) via llvm-dev <llvm-dev at lists.llvm.org> wrote: > [Resending due to

> On May 29, 2018, at 12:28 PM, David Blaikie <dblaikie at gmail.com> wrote: > > +some of the debug info cabal (& Duncan, as an emeritus member, and person who plumbed a lot of the current debug info syntax support in) > > Visitor seems plausible though I haven't looked at the code in detail to see if it'd work perfectly. > > On Tue, May 29, 2018 at 7:56

[Resending due to accidental markdown rendering - sorry] Hi list, Let's talk about adding a new type of debug info metadata. Here are the steps (at minimum - probably incomplete) one needs to take: 1. Create a new class in the hierarchy 2. Implement two forms of `MD_NODE_GET` 3. Specialize `MDNodeKeyImpl` 4. Modify `LLParser.cpp` and add serialization code for your special type5. Modify

> On May 29, 2018, at 15:33, Sohail Somani (Fizz Buzz Inc.) <sohail at fizzbuzzinc.com> wrote: > > Thanks all for your response. > > On Tue, May 29, 2018, at 5:38 PM, Duncan P. N. Exon Smith wrote: >> >> >>> On May 29, 2018, at 12:55, Adrian Prantl <aprantl at apple.com> wrote: >>> >>> >>> >>>> On May 29,

Thanks all for your response. On Tue, May 29, 2018, at 5:38 PM, Duncan P. N. Exon Smith wrote: > > >> On May 29, 2018, at 12:55, Adrian Prantl <aprantl at apple.com> wrote: >> >> >> >>> On May 29, 2018, at 12:28 PM, David Blaikie <dblaikie at gmail.com> wrote: >>> >>> +some of the debug info cabal (& Duncan, as an

Hi, list, suppose i have such a data frame: trash <- data.frame(cbind(seq(1:5),c('a','a','b','a','b'),c('b','a','b','b','a'))) names(trash) <- c('age','typeI','typeII') and I want to change all 'a's to be 0 and 'b's to be 1. temp <- as.matrix(trash)

Drivers have no business looking into dma-mapping internals and check what backend is used. Unfortunstely the DRM core is still broken and tries to do plain page allocations instead of using DMA API allocators by default and uses various bandaids on when to use dma_alloc_coherent. Switch nouveau to use the same (broken) scheme as amdgpu and radeon to remove the last driver user of

Regarding flags, I was just thinking that maybe we should invent a new DISubprogramFlags type. DISubprogram already has a few bitfields for subprogram-specific things, Fortran will want 3 more, and there's no reason to fill up the generic DIFlags with more bits that are used in only one class. I agree that the array stuff needs to be designed with an eye to handling how other languages do

Hi all, I have been struggling with ANOVAs on R. I am new to R, so I created a simple data frame, and I do some analyses on R just to learn R and then check them on SPSS to make sure that I am doing fine. Here is the problem that I've run into: when we use the aov function, it uses SS Type I as default (on SPSS it is Type III). Then I used the Anova function under cars package using the

Hi guys, Just wanted to give you a heads up, so you don't end up chasing strange issues... Since early this morning, our Tipping Point IPS is blocking the Asterisk generated SIP Quality messages (the ones which tell you how good or badly reachably a remote SIP server is) Rule 5051: SIP: PROTOS Test Suite INVITE Test Case This filter detects a test case from the PROTOS SIP testing

Hi all, I have been trying to calculate Type III SS in R for an unbalanced two-way anova. However, the Type III SS are lower for the first factor compared to type I but higher for the second factor (see below). I have the impression that Type III are always lower than Type I - is that right? And a clarification about how to fit Type III SS. Fitting model<-aov(y~a*b) in the base package and

Hi all, this little series removes the last swiotlb API exposed to modules. Diffstat: arch/x86/include/asm/xen/swiotlb-xen.h | 6 ------ arch/x86/kernel/pci-dma.c | 28 ++++------------------------ drivers/gpu/drm/nouveau/nouveau_ttm.c | 10 +++------- drivers/pci/xen-pcifront.c | 6 ------ kernel/dma/swiotlb.c | 1 - 5 files changed, 7

On Jun 12, 2011, at 5:31 PM, Sohail Somani wrote: > On 11-06-12 7:40 PM, John McCall wrote: >> On Jun 12, 2011, at 2:14 PM, Cameron Zwarich wrote: >> >>>> On Jun 12, 2011, at 1:25 AM, Duncan Sands wrote: >>>> >>>>>> Hi Sohail, >>>>>> >>>>>>>> Is LLVM expressive enough to represent asynchronous

On Jun 12, 2011, at 5:53 PM, John McCall wrote: > > On Jun 12, 2011, at 5:31 PM, Sohail Somani wrote: > >> On 11-06-12 7:40 PM, John McCall wrote: >>> On Jun 12, 2011, at 2:14 PM, Cameron Zwarich wrote: >>> >>>>> On Jun 12, 2011, at 1:25 AM, Duncan Sands wrote: >>>>> >>>>>>> Hi Sohail,

On 11-06-12 12:01 AM, Sohail Somani wrote: > Is LLVM expressive enough to represent asynchronous exceptions? > --------------------------------------------------------------- > > Summary: Need new LLVM instructions or extending of all instructions. > > C++ exceptions are synchronous: the compiler knows when/where they are > being raised. > > Asynchronous exceptions can

Hi, I am trying to install a bunch of packages via command line and can use some help in getting it right. My env is a freshly setup OpenSuse 11.4 on an amd desktop. I have not yet installed gcc (Will I need gcc to install packages? I have installed make, assuming R might need it.). I have tried it both under R2.12 and R2.13. I have a list of packages to install such as fImport, fGarch, zoo,

Asterisk gurus, To have analog call progress (which as far as I know asterisk does not have right now) does it not come down to 4 states to detect - and I hope that some asterisk gurus can implement those 4 states easily. I see this as 4 states: Busy - a 50% duty cycle Ringing - a % on duty and MORE of a bigger % off duty cycle - or basically not BUSY and not TALK detect Talk - something

Sometimes to_json options feels abusing to me: user.to_json(:only => [:id, :name], :methods => [:something]) I would prefer an API like this instead: user.to_json(:id, :name, :something) What do you think about adding a use case like this to to_json? -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To view this

Hello all, Thank you very much for viewing the letter. This is Haowei (English name: Cyrus Evans) from China, who is a professiona IT editor and English interpretor. As I have gained more than 3 years' experience of localizatioin work and so much experience opensource software (including mybboard, smf etc.). As an experienced contributor, I wirte this letter to apply for joining