search for: union

...1: SEC_ACE_FLAG_SUCCESSFUL_ACCESS 0: SEC_ACE_FLAG_FAILED_ACCESS size : 0x0038 (56) access_mask : 0x00000020 (32) object : union security_ace_object_ctr(case 7) object: struct security_ace_object flags : 0x00000003 (3) 1: SEC_ACE_OBJECT_TYPE_PRESENT 1: SEC_ACE_INHERITED_OBJECT_TYPE_PRES...

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

...gt; > -Chris > > -- -- Talin -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20100112/de2f07ac/attachment.html> -------------- next part -------------- A non-text attachment was scrubbed... Name: unionref.patch Type: application/octet-stream Size: 8332 bytes Desc: not available URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20100112/de2f07ac/attachment.obj>

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

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

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

2010/1/14 Talin <viridia at gmail.com>: > The reason for doing it this way is that to construct a union, you really > need 4 pieces of information: The type of the union, the type and value of > the member to be initialized, and the index of which member is being > initialized. Does requiring the index mean that uniquing the union type will have to re-write many of the corresponding insertv...

On Jan 12, 2010, at 5:01 PM, Talin wrote: > Here is the LangRef part of the patch. > +<p>The union type is used to represent a set of possible data types which can > + exist at a given location in memory (also known as an "untagged" > + union). [...] This wording is somewhat misleading; memory in LLVM has no types. How about: "A union type describes an object with size...

On Tue, Feb 14, 2017 at 11:22 PM, Steven Perron <perrons at ca.ibm.com> wrote: > 3) How should we handle a reference directly through a union, and a > reference that is not through the union? > > My solution was to look for each member of the union overlaps the given > offset, and see if any of those members aliased the other reference. If no > member aliases the other reference, then the answer is no alias. Otherwise &g...

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

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

...description found for parameter 'migratetype' >> mm/page_alloc.c:4663: warning: No description found for parameter 'page' include/net/cfg80211.h:1738: warning: No description found for parameter 'report_results' include/net/cfg80211.h:1738: warning: Excess struct/union/enum/typedef member 'results_wk' description in 'cfg80211_sched_scan_request' include/net/cfg80211.h:1738: warning: No description found for parameter 'report_results' include/net/cfg80211.h:1738: warning: Excess struct/union/enum/typedef member 'results_wk' de...

...description found for parameter 'migratetype' >> mm/page_alloc.c:4663: warning: No description found for parameter 'page' include/net/cfg80211.h:1738: warning: No description found for parameter 'report_results' include/net/cfg80211.h:1738: warning: Excess struct/union/enum/typedef member 'results_wk' description in 'cfg80211_sched_scan_request' include/net/cfg80211.h:1738: warning: No description found for parameter 'report_results' include/net/cfg80211.h:1738: warning: Excess struct/union/enum/typedef member 'results_wk' de...

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

On Tue, Jan 12, 2010 at 5:46 PM, Dan Gohman <gohman at apple.com> wrote: > > On Jan 12, 2010, at 5:01 PM, Talin wrote: > > > Here is the LangRef part of the patch. > > > +<p>The union type is used to represent a set of possible data types > which can > > + exist at a given location in memory (also known as an "untagged" > > + union). > [...] > > This wording is somewhat misleading; memory in LLVM has no types. > How about: > > &quot...

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

On Thu, Jan 14, 2010 at 9:25 PM, me22 <me22.ca at gmail.com> wrote: > 2010/1/14 Talin <viridia at gmail.com>: > > The reason for doing it this way is that to construct a union, you really > > need 4 pieces of information: The type of the union, the type and value > of > > the member to be initialized, and the index of which member is being > > initialized. > > Does requiring the index mean that uniquing the union type will have > to re-write...

So, https://bugs.llvm.org/show_bug.cgi?id=32056 is an example showing our current TBAA tree for union generation is definitely irretrievably broken. I'll be honest here. I'm pretty sure your proposal doesn't go far enough. But truthfully, I would rather see us come closer to a representation we know works, which is GCC's. Let me try to simplify what you are suggesting, and what we...

On Jan 6, 2010, at 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. H...