search for: unions

I tried your suggestion but still no luck, starting to think my domain is broken :( I did a debug when doing the migrate, not so if this will help On Thu, Nov 1, 2018 at 10:28 AM Rowland Penny via samba < samba at lists.samba.org> wrote: > On Thu, 1 Nov 2018 07:21:57 +0200 > Eben Victor <eben.victor at gmail.com> wrote: > > > I've been been trying to investigate

I've been been trying to investigate this for sometime now, hence I came to the experts :) I have rejoined all my DC's with new names, see below. ;; ANSWER SECTION: <domain>.corp. 3600 IN NS psad101zatcrh.<domain>.corp. -> New rebuild, new hostname, RHEL6 to RHEL7 upgrade <domain>.corp. 3600 IN NS prdc001zafsrh.<domain>.corp. -> New

Here is the LangRef part of the patch. On Tue, Jan 12, 2010 at 2:11 PM, Chris Lattner <clattner at apple.com> wrote: > > On Jan 11, 2010, at 4:30 PM, Talin wrote: > > I'm working on a new version of the patch. >> >> Another thing I wanted to ask about - do you prefer to have one giant >> patch that has everything, or a series of incremental patches? I can

On Fri, Jan 15, 2010 at 11:02 AM, Dan Gohman <gohman at apple.com> wrote: > > On Jan 13, 2010, at 12:11 PM, Talin wrote: > > > > It depends on whether or not unions can be passed around as SSA values or > not. I can think of situations where you would want to. > > I'm skeptical that you *really* want to (i.e. that you wouldn't > be better off just writing helper functions in your front-end > which do the addressing and load/store and the...

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...

I'm still working on the next patch, it's going somewhat slowly. I wanted to create a unit test that actually created a union, and in order to do that I had to implement constant unions. And rather than creating a special syntax for constructing a union, I decided that it was simplest to implement the insertvalue instruction for a constant union expression: @foo = constant union { i32, float } insertvalue union { i32, float } undef, i32 4, 0 What this says is to start with a...

...g insertvalue calls? For instance, how would this round-trip? @foo = constant union { float, i32 } insertvalue union { i32, float } undef, i32 4, 0 @bar = constant union { i32, float } insertvalue union { float, i32 } undef, i32 4, 1 I'm very glad to see a non-bitcast method of using unions, BTW.

...nion). [...] This wording is somewhat misleading; memory in LLVM has no types. How about: "A union type describes an object with size and alignment suitable for an object of any one of a given set of types." Also, is it really useful to support insertvalue/extractvalue/getelementptr on unions? The benefit of unions that I'm aware of is it allows target-independent IR to work with appropriately sized and aligned memory. This doesn't require any special support for accessing union members; for example: %p = alloca union { i32, double } %q = bitcast union { i32, double }* %p t...

...reference. If no > member aliases the other reference, then the answer is no alias. Otherwise > the answer is may alias. The run time for this would be proportional to > "distance to the root" * "number of overlapping members". This could be > slow if there are unions with many members or many unions of unions. > > Another option is to say that they do not alias. This would mean that all > references to unions must be explicitly through the union. >From what I gather from the thread so far, the access through the union may be lost because of LLVM t...

On Fri, Jan 15, 2010 at 3:13 PM, Talin <viridia at gmail.com> wrote: > On Fri, Jan 15, 2010 at 11:02 AM, Dan Gohman <gohman at apple.com> wrote: > >> >> On Jan 13, 2010, at 12:11 PM, Talin wrote: >> > >> > It depends on whether or not unions can be passed around as SSA values >> or not. I can think of situations where you would want to. >> >> I'm skeptical that you *really* want to (i.e. that you wouldn't >> be better off just writing helper functions in your front-end >> which do the addressing an...

On Friday 02 January 2009 20:48:25 Chris Lattner wrote: > 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...

Hello all, I'm new to the llvm community. I'm learning how things work. I noticed that there has been some interest in improving how unions are handled. Bug 21725 is one example. I figured it might be a interesting place to start. I discussed this with a couple people, and below is a suggestion on how to represent unions. I would like some comments on how this fits in with how things are done in llvm. Later, Steven Perron Moti...

Hi Wei, [auto build test WARNING on linus/master] [also build test WARNING on v4.11 next-20170504] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url: https://github.com/0day-ci/linux/commits/Wei-Wang/Extend-virtio-balloon-for-fast-de-inflating-fast-live-migration/20170505-052958 reproduce: make htmldocs All warnings (new ones prefixed by

Hi Wei, [auto build test WARNING on linus/master] [also build test WARNING on v4.11 next-20170504] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url: https://github.com/0day-ci/linux/commits/Wei-Wang/Extend-virtio-balloon-for-fast-de-inflating-fast-live-migration/20170505-052958 reproduce: make htmldocs All warnings (new ones prefixed by

On Jan 2, 2009, at 2:29 PM, Jon Harrop wrote: >>> I don't think you would want to build discriminated unions on top of >>> C-style unions though. >> >> Why? > > Uniformity when nesting and space efficiency. Users of a language > front-end > will want to nest discriminated unions, e.g. to manipulate trees. Okay, so you're just talking about boxed vs unboxed discrimin...

...eading; memory in LLVM has no types. > How about: > > "A union type describes an object with size and alignment suitable for > an object of any one of a given set of types." > OK > > Also, is it really useful to support > insertvalue/extractvalue/getelementptr on unions? The benefit of unions > that I'm aware of is it allows target-independent IR to work with > appropriately sized and aligned memory. This doesn't require any special > support for accessing union members; for example: > > %p = alloca union { i32, double } > %q = bitcast...

I've been thinking about how to represent unions or "disjoint types" in LLVM IR. At the moment, the only way I know to achieve this right now is to create a struct that is as large as the largest type in the union and then bitcast it to access the fields contained within. However, that requires that the frontend know the sizes of all of...

.... However, from the standpoint of a frontend, this is not a great concern, because the frontend will most likely sort the list of types before constructing the IR type. By always putting the types in a canonical order, regardless of the order that they appear in the source code, you can ensure that unions of equal types are always compatible. In other words, you can treat the members like an ordered set rather than like a list. > > I'm very glad to see a non-bitcast method of using unions, BTW. > -- -- Talin -------------- next part -------------- An HTML attachment was scrubbed... U...

...hild of every union/struct it needs to be (lack of multiple parents means you can't just frob them all to offset zero). Your suggestion is to invert this as a struct short int | / union We don't allow multiple parents, however. Because of that, you suggest we follow all nodes for unions, special casing union-type nodes somehow Let me suggest something different: We know the current structure fails us in a number of ways. Instead of trying to shoehorn this into our current structure, I suggest: we stop messing around and just have a GCC style tree, and represent the children inst...

...12:45 PM, Talin wrote: > This patch adds a UnionType to DerivedTypes.h. Cool. When proposing an IR extension, it is usually best to start with a LangRef.html patch so that we can discuss the semantics of the extension. Please do write this before you get much farther. I assume that you want unions usable in the same situations as a struct. However, how do "constant unions" work? How do I initialize a global variable whose type is "union of float and i32" for example? > It also adds code to the bitcode reader / writer and the assembly parser for the new type, as well...