search for: disubrang

Hi, To improve debug information for variable length arrays (https://bugs.llvm.org/show_bug.cgi?id=30553) I have proposed some changes to Metadata IR's DISubrange node. To get some wider visibility on this, I'm sharing this as an RFC with llvm-dev. The proposed change is to extend the 'count' field to also accept a Metadata node, rather than only accepting a signed integer. For example: !10 = !DILocalVariable(name: "count", scope:...

...W_AT_type: int DW_AT_lower_bound: 2 DW_AT_upper_bound: 11 2.2.2 Adjustable arrays By adjustable arrays, we mean that an array may have its size passed explicitly as another argument. SUBROUTINE subr2(array2,N) INTEGER :: N TYPE(t) :: array2(N) In this case, the compiler expresses the !DISubrange as an expression that references the dummy argument, N. call void @llvm.dbg.declare(metadata i64* %N, metadata !113, metadata !DIExpression()) … !110 = !DIFortranArrayType(baseType: !7, elements: !111) !111 = !{ !112 } !112 = !DIFortranSubrange(lowerBound: 1, upperBound: !113, upperBoundExpre...

...e_type: DW_AT_type: int DW_AT_lower_bound: 2 DW_AT_upper_bound: 11 2.2.2 Adjustable arrays By adjustable arrays, we mean that an array may have its size passed explicitly as another argument. SUBROUTINE subr2(array2,N) INTEGER :: N TYPE(t) :: array2(N) In this case, the compiler expresses the !DISubrange as an expression that references the dummy argument, N. call void @llvm.dbg.declare(metadata i64* %N, metadata !113, metadata !DIExpression()) … !110 = !DIFortranArrayType(baseType: !7, elements: !111) !111 = !{ !112 } !112 = !DIFortranSubrange(lowerBound: 1, upperBound: !113, upperBoundExpression...

On 21 February 2011 19:35, Devang Patel <dpatel at apple.com> wrote: > If you have patch, go ahead, I am fine with it. I don't, but can produce one. Will look into it tomorrow morning. cheers, --renato

...or ArrayType, we create it like this: > SmallVector<llvm::Value *, 8> Subscripts; > ... > Subscripts.push_back(DBuilder.getOrCreateSubrange(0, Count)); > ... > llvm::DIArray SubscriptArray = DBuilder.getOrCreateArray(Subscripts); > > The elements of getTypeArray() are DISubranges, even though the function is > called getTypeArray :) Yeah, that seems pretty bogus. They could use a separate type with its own array handling, perhaps. > >> >> >> > We can fix that by extending DICompositeType to DISubroutineType and >> > only >> >...

On Fri, Feb 18, 2011 at 1:52 PM, Renato Golin <rengolin at systemcall.org>wrote: > On 18 February 2011 21:34, Talin <viridia at gmail.com> wrote: > > Sorry, I meant DIBuilder. > > DIBuilder is the new DIFactory. I've been playing with it this week > and it's much easier and straightforward to use. I'm still having > problems to create arrays, though.

On Mon, Jul 21, 2014 at 3:35 PM, Manman Ren <manman.ren at gmail.com> wrote: > > > > On Mon, Jul 21, 2014 at 1:14 PM, David Blaikie <dblaikie at gmail.com> wrote: >> >> On Mon, Jul 21, 2014 at 10:39 AM, Manman Ren <manman.ren at gmail.com> wrote: >> > >> > >> > >> > On Mon, Jul 14, 2014 at 11:32 AM, Manman Ren

...il/llvm-dev/2018-January/120098.html) on ideas to remove the need for these, on requirements from out-of-tree backends, and on supporting the same functionality in GlobalISel. * Sander De Smalen has shared an [RFC](http://lists.llvm.org/pipermail/llvm-dev/2018-January/120129.html) on extending the DISubrange count field, which can be used to improve debug information for variable length arrays or SVE vectors. * Daniel Neilson has [resurrected](http://lists.llvm.org/pipermail/llvm-dev/2018-January/120080.html) a set of patches from 2015 to modify memcpy/memmove/memset to have destination and source al...

Hi. I searched and the closest thing I could find was this http://lists.llvm.org/pipermail/llvm-dev/2018-February/121348.html Currently a known sized array looks and debugs as expected. I use llvm.dbg.declare with DICompositeType tag: DW_TAG_array_type and the size field. In my language arrays are always passed around with a pointer and size pair. I'd like debugging to show up as nicely

Hi, I see things like this. What does it mean? Is it documented somewhere? Thanks. ; preds = %for.body https://llvm.org/docs/LangRef.html ; <label>:91: ; preds = %88 %92 = load i8**, i8*** @glob_complete_word.matches, align 8, !dbg !99798 %93 = load i32, i32* @glob_complete_word.ind, align 4, !dbg !99799 %94 = sext i32 %93 to i64, !dbg !99798