search for: subrange

...4 <1>< 141> DW_TAG_base_type DW_AT_byte_size 4 DW_AT_encoding DW_ATE_signed <1>< 144> DW_TAG_array_type DW_AT_type <134> <2>< 149> DW_TAG_subrange_type DW_AT_type <141> DW_AT_upper_bound <141>1 [...] gcc 3/4: [...] LOCAL_SYMBOLS: [...] <2>< 66> DW_TAG_variable DW_AT_name i DW_AT_decl_file...

...4 <1>< 141> DW_TAG_base_type DW_AT_byte_size 4 DW_AT_encoding DW_ATE_signed <1>< 144> DW_TAG_array_type DW_AT_type <134> <2>< 149> DW_TAG_subrange_type DW_AT_type <141> DW_AT_upper_bound <141>1 [...] gcc 3/4: [...] LOCAL_SYMBOLS: [...] <2>< 66> DW_TAG_variable DW_AT_name i DW_AT_decl_file...

On Feb 11, 2012, at 7:51 AM, Yuri Pankov <yuri.pankov at gmail.com> wrote: > Hi, > > ctfconvert is particularly unhappy about that (e.g., ERROR: ctfconvert: > die 141: base type without name). Is it intended behavior? Not that I know of, please file a bug. Thanks! -eric

...terCoalescer.cpp#L1871), the new live interval looks like this: %0 [16r,32B:2)[32B,96r:0)[96r,128B:1) 0 at 32B-phi 1 at 96r 2 at 16r L0000000000000003 [32B,80B:0) 0 at 32B-phi // sub0 This remaining [32B,80B:0) across %bb.1 is a fake phi-only segment. If I freshly recompute LiveIntervals, the subrange is empty as it should be. The verifier doesn't care about this, however it does end up confusing RenameIndependentSubregs. After RenameIndependentSubregs, this becomes %0 [24r,24d:0)[104r,104d:1) 0 at 24r 1 at 104r L0000000000000003 [24r,24d:1)[104r,104d:2) which fails the verifier with "...

...7/twitter-crashes-itself-with-commas?1 Also, I've seen some recursion-related PR's in Clang, although I think that they are usually related to templates and not parsing. Also, it's easy to blow stack in quicksort if you don't tail call into the recursive invocation of the _larger_ subrange. Recursively calling into the smaller subrange guarantees that it's size is less than half of the current range, whereas a non-tail call into the larger subrange can require linear stack space if the partition isn't good. > You're distracting this man from his job of learning how to...

Are there any plans to support generation of DWARF DIEs needed for languages other than C, C++, and Obj-C? For example, ADA would need more capability and so would several other "experimental" new languages that use LLVM. Just as one simple example, the "subrange" type can be used with variables in many languages. Right now, LLVM only supports "subrange" in the context of an array index, but not as a first class type. bagel

...const std::string &Name = "", Instruction *InsertBefore = 0, Is it acceptable to just make the template argument be the container? That way you could pass: std::vector.. V; ... new CallInst(Callee, V, "foo"); etc. The disadvantage is that you lose the ability to pass a subrange. However, if you know you're using a subrange, you should be able to use another ctor form. -Chris -- http://nondot.org/sabre/ http://llvm.org/

...ef,read-undef> = ... 32B %vreg0:ssub_1<def> = ... 48B = %vreg0 64B = %vreg0:ssub_0 80B %vreg0 = ... 96B = %vreg0:ssub_1 will be represented as the following live range(s): Common LiveRange: [16r,32r)[32r,64r),[80r,96r) SubRange with Mask 0x0004 (=ssub_0): [16r,64r)[80r,80d) SubRange with Mask 0x0008 (=ssub_1): [32r,48r)[80r,96r) Patches/Changes: * Moves live range management code in the LiveInterval class to a new class LiveRange, move the previous LiveRange class (which was just a single interval inside a live...

...r 2 at 208r L00000002 [96r,96d:1)[112r,288r:0) 0 at 112r 1 at 96r L00000030 [208r,288r:1) 0 at x 1 at 208r L00000001 [96r,288r:0) 0 at 96r Copy+Merge 00000030 into 00000020 Reduce Lane to 00000010 conflict at %vreg34:1 at 240r *** Couldn't join subrange! UNREACHABLE executed at /d/en/johnsoni-0/gctools/llvm/lib/CodeGen/RegisterCoalescer.cpp:2693! #0 0x00000000027395af llvm::sys::PrintStackTrace(llvm::raw_ostream&) /d/en/johnsoni-0/gctools/llvm/lib/Support/Unix/Signals.inc:402:0 #1 0x0000000002739971 PrintStackTraceSignalHandler(void*) /d/en/j...

On Wed, Oct 3, 2012 at 10:15 AM, Matthieu Moy <Matthieu.Moy at grenoble-inp.fr> wrote: > Preston Briggs <preston.briggs at gmail.com> writes: >> Think about costs asymptotically; that's what matters. Calls and >> returns require constant time, just like addition and multiplication. > > Constant time, but not necessarily constant memory. > > Deep recursion

...= ... > 48B = %vreg0 > 64B = %vreg0:ssub_0 > 80B %vreg0 = ... > 96B = %vreg0:ssub_1 > > will be represented as the following live range(s): > > Common LiveRange: [16r,32r)[32r,64r),[80r,96r) > SubRange with Mask 0x0004 (=ssub_0): [16r,64r)[80r,80d) > SubRange with Mask 0x0008 (=ssub_1): [32r,48r)[80r,96r) > > Patches/Changes: > * Moves live range management code in the LiveInterval class to a new > class LiveRange, move the previous LiveRange class (which was &g...

...> back end, although that seems to have regressed. > > This work has been stalled since sometime last spring, with the discovery that the > debug info passed through LLVM is in fact, equivalent to only a small subset of > Dwarf. The decisive discovery was that the debug info for a subrange type does not > allow a base type to be noted, even though Dwarf does. Modula-3 allows subranges > of any of a few builtin types and an extremely large potential set of programmer-defined > enumeration types, so this is pretty much unusable for subranges. We are certainly interested in s...

On Monday 02 July 2007 23:24, David A. Greene wrote: > > > - Changing the API > > > a) Template it to take two iterators. This causes code size bloat. > > This seems like the right solution to me. Unless llvm is running on > extremely limited memory embedded systems, the extra code space > shouldn't be an issue. It turns out this wasn't quite a simple as

...>> 48B = %vreg0 >> 64B = %vreg0:ssub_0 >> 80B %vreg0 = ... >> 96B = %vreg0:ssub_1 >> >> will be represented as the following live range(s): >> >> Common LiveRange: [16r,32r)[32r,64r),[80r,96r) >> SubRange with Mask 0x0004 (=ssub_0): [16r,64r)[80r,80d) >> SubRange with Mask 0x0008 (=ssub_1): [32r,48r)[80r,96r) >> >> Patches/Changes: >> * Moves live range management code in the LiveInterval class to a new >> class LiveRange, move the previous LiveRange class (which wa...

...bugging.html and some things aren't clear. There are a couple of references made to %llvm.dbg.variable, which isn't defined anywhere. It it an intrinsic? A global? Could it be a relic from the old debug info docs (where it *is* defined?). The same goes for llvm.dbg.derivedtype and llvm.dbg.subrange which are also referenced but not defined. Additionally, there's this definition: """  void %llvm.dbg.declare(metadata, metadata) This intrinsic provides information about a local element (ex. variable.) The first argument is metadata holding alloca for the variable.. The seco...

...om, dom1.example.com, dom2.example.com, and the primary user of the machine is in users.example.com, is it OK to have config like this: > > idmap config * : backend = autorid > > idmap config * : range = <range> > > idmap config * : rangesize = <subrange> > > idmap config USERS : backend = rid > > idmap config USERS : range = <range> > > > > If yes, what about the same config for the case when USERS (users.example.com) is the only domain? My understanding is in a single domain situation this config...

...a forest of, say, users.example.com, dom1.example.com, dom2.example.com, and the primary user of the machine is in users.example.com, is it OK to have config like this: idmap config * : backend = autorid idmap config * : range = <range> idmap config * : rangesize = <subrange> idmap config USERS : backend = rid idmap config USERS : range = <range> If yes, what about the same config for the case when USERS (users.example.com) is the only domain? My understanding is in a single domain situation this config shouldn't cause any issues with '...

...gt;> 48B = %vreg0 >> 64B = %vreg0:ssub_0 >> 80B %vreg0 = ... >> 96B = %vreg0:ssub_1 >> >> will be represented as the following live range(s): >> >> Common LiveRange: [16r,32r)[32r,64r),[80r,96r) >> SubRange with Mask 0x0004 (=ssub_0): [16r,64r)[80r,80d) >> SubRange with Mask 0x0008 (=ssub_1): [32r,48r)[80r,96r) >> >> Patches/Changes: >> * Moves live range management code in the LiveInterval class to a new >> class LiveRange, move the previous LiveRange class (which w...

...s/btrfs/ioctl.c @@ -2223,8 +2223,6 @@ static noinline long btrfs_ioctl_clone(struct file *file, unsigned long srcfd, * decompress into destination''s address_space (the file offset * may change, so source mapping won''t do), then recompress (or * otherwise reinsert) a subrange. - * - allow ranges within the same file to be cloned (provided - * they don''t overlap)? */ /* the destination must be opened for writing */ @@ -2247,8 +2245,6 @@ static noinline long btrfs_ioctl_clone(struct file *file, unsigned long srcfd, src = src_file->f_dentry->d_i...

I am, as this question will make very obvious, not exactly a guru when it comes to audio under Linux. I'd like to record some prompts using a nice microphone and my Ensoniq sound card, and then convert them to gsm/wav for use with asterisk. What Linux command would I use to a) do the recordings, and then b) convert them to the appropriate formats? I know there are