similar to: [LLVMdev] improving constant/type uniquing

Chris asked me to look into improving the current sad state of ConstantUniqueMap, and by coincidence Meador Inge started working on the same thing on his own initiative, so I'm writing down a concrete proposal to make sure we're not working at cross purposes. The ConstantUniqueMap template class is used to store unique instances of ConstantStruct, ConstantVector, ConstantArray,

On 10 July 2011 19:47, Talin <viridia at gmail.com> wrote: > However, I would imagine other uses for this facility. What this effectively > is "metadata for types", although unlike metadata nodes this data would be > immutable. Hi Talin, The new type system allows you to name types and, if I got it rght, that's unique and immutable. You could use that fact, plus

I'd like to figure out a clean way to annotate LLVM types with additional information. This is related to the garbage collection discussion - I'd like to figure out a good way to do this, so I can add it to the proposal. Basically what I want is to be able to take a Constant and associate it with a type, such that (1) any backend pass that has a reference to the type can quickly and

All, This buildbot is getting lots of assertion failures in the test suite. They were probably caused by my commit: ------------------------------------------------------------------------ r151049 | foad | 2012-02-21 09:25:52 +0000 (Tue, 21 Feb 2012) | 6 lines Changed paths: M /llvm/trunk/lib/VMCore/LLVMContextImpl.h M /llvm/trunk/lib/VMCore/Type.cpp PR1210: make uniquing of struct and

With the help of the Rails Recipes have got a self-referential HABTM relationship working, but I''m really struggling with getting a new entry from a form accepted. i should say here that the form is also submitting info for the join table too. So in my model I have: class Type < ActiveRecord::Base has_and_belongs_to_many :subtypes, :class_name => ''Type'',

I got the following: > library(foreign) > swal = read.spss("swallowing.sav", to.data.frame =TRUE) Warning message: In read.spss("swallowing.sav", to.data.frame = TRUE) : swallowing.sav: Unrecognized record type 7, subtype 21 encountered in system file > The bulk of the data seems to read in a usable form, but I'm curious about what might be getting lost

On Tue, Feb 21, 2012 at 4:51 AM, Jay Foad <jay.foad at gmail.com> wrote: > All, > > This buildbot is getting lots of assertion failures in the test suite. > They were probably caused by my commit: > > ------------------------------------------------------------------------ > r151049 | foad | 2012-02-21 09:25:52 +0000 (Tue, 21 Feb 2012) | 6 lines > Changed paths: >

On Jan 24, 2011, at 11:57 PM, Duncan Sands wrote: > Hi Talin, > >> Really, all I need to make this work is some way to 'mark' a global so that my >> custom pass can query for all marked globals. Any ideas on this? > > metadata maybe? A better approach would be to create an global array of strings to hold names of marked globals. You know the name of this special

On Jan 30, 2011, at 8:36 PM, Talin wrote: > So, I spent the better part of a day making sure that each and every static global had a well-formed and unique name. So far so good. > > However, It turns out that what I need is a little different than what I described - I not only need to know which globals should be traced, but I also need to associate with each of these globals a data

Hello, I''m creating my own Tumblr [tumblr.com] like rails app. It''s like a blog, but in this case a blog post could be of a certain type, i.e. a regular post, a video, a link, a photo, a song(info). Well now, it''s clear that they share a lot of similar functionality: title, created_at/updated_at, commentable, probably has an author_id, etc.. But besides that they are

What's the current status on support for first-class structs? The last I heard was: - Structs which are smaller or equal to two pointers can be passed / returned / loaded / stored by value. - There are plans to expand this in the future to support arbitrary-sized structs as first class values. (Probably via some transformation pass the converts the return value into a hidden

On Mon, Mar 7, 2011 at 4:08 AM, nicolas geoffray <nicolas.geoffray at gmail.com > wrote: > Hi Talin, > > On Sat, Mar 5, 2011 at 6:42 PM, Talin <viridia at gmail.com> wrote: >> >> >> So I've been thinking about your proposal, that of using a special address >> space to indicate garbage collection roots instead of intrinsics. > > > Great!

On Tue, Jan 25, 2011 at 9:14 AM, Devang Patel <dpatel at apple.com> wrote: > > On Jan 24, 2011, at 11:57 PM, Duncan Sands wrote: > > > Hi Talin, > > > >> Really, all I need to make this work is some way to 'mark' a global so > that my > >> custom pass can query for all marked globals. Any ideas on this? > > > > metadata maybe?

On Dec 20, 2009, at 12:27 AM, Talin wrote: > What's the current status on support for first-class structs? The last I heard was: > Structs which are smaller or equal to two pointers can be passed / returned / loaded / stored by value. > There are plans to expand this in the future to support arbitrary-sized structs as first class values. (Probably via some transformation pass the

On Jun 25, 2013, at 11:35 AM, David Blaikie wrote: > On Tue, Jun 25, 2013 at 10:13 AM, Manman Ren <mren at apple.com> wrote: >> >> On Jun 25, 2013, at 9:15 AM, David Blaikie <dblaikie at gmail.com> wrote: >> >> On Tue, Jun 25, 2013 at 8:59 AM, Manman Ren <mren at apple.com> wrote: >> >> >> Any suggestion on how to move this

Hi all, This is perhaps more a statistics question than an R question, but I hope it's OK anyhow. I have some data (see below) with the number of tests positive to subtype H1 of a virus, the number of tests postive to subtype H3, and the total number of tests. This is for two different groups, and the two subtypes are mutually exclusive. What is the best way to test if the proportion of H1

On Tue, Feb 14, 2012 at 2:44 AM, Chris Lattner <clattner at apple.com> wrote: > On Feb 13, 2012, at 2:00 AM, Talin wrote: > > Just out of curiosity, why not MurmurHash3 ? This page seems to >> suggest that #2 has some flaw, and #3 is better all round: >> >> https://sites.google.com/site/murmurhash/ >> >> The main reason is because there's no

Thanks for the heads up Chris. Talin, how is your GC dealing with non-pointers (be it allocas or not)? What is the use-case (either in C or LLVM)? Nicolas On Fri, Sep 24, 2010 at 7:00 PM, Chris Lattner <clattner at apple.com> wrote: > On Sep 22, 2010, at 8:52 AM, Talin wrote: > > I'm moving this thread to llvm-dev in the hopes of reaching a wider > audience. > >

Having jotted down some models, with some inheritence I tried to run some unit tests. After waiting for rake test_units to run I got a rake of errors (if you''ll forgive the play on words). The errors were to do with unknown tables in the tear down stage. The unknown tables corresponded to sub-types where single table inheritence was used. In other words, these tables *shouldn''t*

First cleanup patch: r185020 Let me know if you have questions. Thanks, Manman On Jun 25, 2013, at 3:56 PM, Eric Christopher wrote: >>> Those parts of the codebase actually trying to handle debug info >>> should be handling valid debug info to begin with - we shouldn't need >>> to call "Verify" all over the place & behave differently (at most it