search for: concret

...l basic block. (3) Imported Entity is handled differently depends on where it is declared, in function lexical scope or in basic block scope. There are two interesting cases where we should consider the representation in dwarf for the above entities: a. Function was not inlined - has one concrete entry. b. Function was inlined - has one abstract entry, one or more inlined entries, and possibly one concrete entry. The goal is to be able to debug all the above entities in case (a) - which is the common case when compile with no optimizations. But also, we would like to be able to deb...

...is handled differently depends on where it is > declared, in function lexical scope or in basic block scope. > > > > There are two interesting cases where we should consider the > representation in dwarf for the above entities: > > a. Function was not inlined - has one concrete entry. > > b. Function was inlined - has one abstract entry, one or more > inlined entries, and possibly one concrete entry. > > > > The goal is to be able to debug all the above entities in case (a) - which > is the common case when compile with no optimizations. But...

...ersion of rails for these applications (, or I don''t have time to fix them...) Is there a way how to ''tell'' the application which version of rails should it use? Or, in other words, is there a way how to run more rails based applications on one machine, each using some concrete version of rails (which may differ)? Thanks, Jozef

As a concrete question, I understand 'Value' class is the parent of many concrete sub-classes. Let's say I retrieve a Value* value = store_inst->getValueOperand(). Unless I know what the sub-type is, how can I further use this object? I tried something like this: ================================...

...M *To: *Jesper Antonsson *Cc: *dag at cray.com, llvm-dev at lists.llvm.org I don’t think you have consensus to move forward at this point in time. My > expectation, which I think represents LLVM’s historical approach, is that a > path to full support be planned out before this effort starts. Concretely, > I expect a real-world backend to be committed to LLVM as a necessary step. > What I meant upthread was: yes it makes sense to do cleanups before landing > a backend, but *someone* has to commit to upstreaming a backend before > you start the cleanups. When I say a backend I don’t...

Hi all, I'm giving a talk in a few days to a group of psychology faculty and grad students re the R statistical language. Most people in my dept. use SAS or SPSS. It occurred to me that it would be nice to have a few concrete examples of things that are fairly straightforward to do in R but that are difficult or impossible to do in SAS or SPSS. However, it has been so long since I have used either of those commercial products that I am drawing a blank. I've searched the forums and web for a list and came up with ju...

I posted something about this a week ago wihtout response, but have made some progress since. However, I''m still not getting exactly what I want. OK, three core tables: create_table :reference_items do |t| t.column :title, :string, :limit => 255 t.column :year, :integer, :limit => 4 t.column :type, :string t.column

...ting a function and pasting those two concepts togther. When I first came accross assign, I thought that was the coolest thing, to be able to output something for each loop. I thought I was smart and R was smart. And yet, lapply makes it way better in almost all the cases. I can make two very concrete suggestions: a) In "An Introduction to R" after: "Warning: for() loops are used in R code much less often than in compiled languages. Code that takes a `whole object' view is likely to be both clearer and faster in R." Give some examples how to avoid it. Mention subset,...

Hi All- As we all know, the C++14 discussion is flaring up again. Chandler brought up that he would like a concrete plan to switch. In my opinion, this is insufficient, as it will result in us simply having this discussion AGAIN next release. Instead, I would prefer us to have a concrete Policy on our host compilers. That way, changes like this are unsurprising to our users, and advance our codebase sufficie...

...g JIT. The scenario is like this: 1. A test code or client code calls a function A() for which a dummy implementation is provided in a library which the test code/client links with during compilation. 2. I create the .bc using -emit-llvm and run it with lli. 3. Now, in the JIT, I have provided the concrete implementation of the function A(). I have to intercept this call to function A() and return a pointer to the concrete implementation in JIT. I tried the way external library symbols are being resolved in JITMemoryManager.cpp but the error I get is as follows: pseudo instructions should be remov...

This patch implements a local buffer reference type for kernel virtual address space and a remote buffer reference type for buffers up to 16 pages based on grant tables. These types are used by the USB driver for bulk data transfer. Signed-off-by: Harry Butterworth <butterwo@uk.ibm.com> _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com

Hi all, We did some benchmarks on code size with clang, gcc 4.5, and open64. Clang performed second in the test. The benchmark is CSiBE. Clang can't compile the linux kernel (some inline asm not supported) and replaypc (error: use of unknown builtin '__builtin_next_arg'). The concrete results are attached. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20100419/32f3e0f4/attachment.html> -------------- next part -------------- A non-text attachment was scrubbed... Name: result-size.png T...

> > > Not sure about this last part. It is really going to require work by us to > rewrite things. :-) In the mean time, I think we should go ahead with this. > FWIW: My problem is, when put in this framework, we will repeatedly make this same decision, this same way, again and again, and never actually get even started on fixing it :) IE "it's just another small

> If there was a concrete need to move to a newer Python version in order to > make lit Python 3 compatible, I would view that as a good reason to move > forward. The concrete need is that users on platforms which ship with Python 3 by default have to put in a workaround (install python2 and patch their $PATH) just...

...M, Andrew Clinton wrote: > This looks like a good extension to the type system. One thing that I > expected to work (when I first tried using opaque types) was for the > optimization passes and verification to operate correctly when using > opaque types, while the type could be made concrete later on - after > optimization. This turned out to be impossible, and in combination with > the lack of naming for opaque types, I decided to avoid their use > entirely. In particular, could you address whether this overhaul of the > type system will address the following: >...

...not like blocking all improvements to InstCombine will > cause a movement to appear to rewrite InstCombine. It will only cause > a shrink in the pool of developers with recent experience working on > InstCombine (and a lot of out-of-tree patches). Frankly, we don't even > have a concrete plan for how we'd do this, or even a target design, > and that's the first item on the critical path to a rewrite. We should > start an RFC and iterate on this until we have a concrete plan and > migration plan. Just want to chime in here in support of what Hal said. I strongl...

...gt; There's a lot of heavily templated code in generic DomTee construction/updater, MemSSA updater, and GraphDiff that has become really hard to modify. For the context, Alina (cc'd) was recently looking into making the domtree code work with 'CFG views'; the basic idea is to take a concrete CFG and a series of updates and create a view over this CFG, as if the updates were applied, add more updates and repeat [1]. The initial attempt was based on GraphDiff and GraphTraits over GraphDiff, but this gets prohibitively verbose very quickly and caused difficult to fix compilation time reg...

On 9 June 2017 at 15:29, Jajoo, Malhar via llvm-dev <llvm-dev at lists.llvm.org> wrote: > Thanks for that , I have read the documentation on this , but I would like to know > if it would be the right thing to do , ie , changing the enum within llvm::Type Well, I find the idea of a non-canonical DummyType slightly disturbing (I don't think it's something we'd ever support

...e? I remember reading somewhere that there is a limit to the number of free email to sms that you can send through AT&T in a given month. Does anyone know anything aobut this? I guess I can believe that it is totally free b/c the receiver is still paying, but I have googled and cannot find any concrete answers. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to rubyonrails-talk-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org To unsubscribe from this gro...

Hello sir, I'm having some problems understading how llvm works. I'm following a concrete example and visualizing the DAG and the .s output and some stuff doesn´t seem to match. I sorry to bother you but I don´t know where I can expose my doubts and I wonder if you could redirect me to some discussion place where someone might help me. Thanks, Patosga _______________________________...