search for: amjad

...CU.finishSubprogramDefinition(SP); <------------- In our case, this code will not be reached for the above subprogram. }); ... } However, the function was optimized out and the code will not call “finishSubprogramDefinition” for it, and attributes will not be added. Regards, Amjad From: David Blaikie [mailto:dblaikie at gmail.com] Sent: Saturday, May 07, 2016 21:38 To: Aboud, Amjad <amjad.aboud at intel.com> Cc: Adrian Prantl <aprantl at apple.com>; llvm-dev <llvm-dev at lists.llvm.org>; Clang Dev <cfe-dev at lists.llvm.org> Subject: Re: Debug info...

...}) DW_AT_name [DW_FORM_strp] ( .debug_str[0x00000060] = "T") DW_AT_decl_file [DW_FORM_data1] ("c:\temp\ICL\LB\retain.cpp") DW_AT_decl_line [DW_FORM_data1] (16) Regards, Amjad From: David Blaikie [mailto:dblaikie at gmail.com] Sent: Saturday, April 30, 2016 17:59 To: Aboud, Amjad <amjad.aboud at intel.com> Cc: Adrian Prantl <aprantl at apple.com>; llvm-dev <llvm-dev at lists.llvm.org>; Clang Dev <cfe-dev at lists.llvm.org> Subject: Re: Debug info...

...: !20) !7 = distinct !DISubprogram(name: "foo<B>", linkageName: "_Z3fooI1BEiPv", scope: !6, file: !6, line: 15, type: !8, isLocal: false, isDefinition: true, scopeLine: 15, flags: DIFlagPrototyped, isOptimized: true, unit: !0, templateParams: !12, variables: !15) Thanks, Amjad --------------------------------------------------------------------- Intel Israel (74) Limited This e-mail and any attachments may contain confidential material for the sole use of the intended recipient(s). Any review or distribution by others is strictly prohibited. If you are not the intended...

On Mon, Nov 9, 2015 at 4:00 AM, Aboud, Amjad <amjad.aboud at intel.com> wrote: > I found a way to skip representing macros in AST and create them directly > in CGDebugInfo through PPCallbacks during preprocessing. > > To do that, I needed to extend ASTConsumer interface with this extra > method: > > > > ///...

...ma (to create an AST) or ASTConsumer. While the CGDebugInfo is only available in the CodeGenModule, which is accessible from BackendConsumer, that implements ASTConsumer. David, skipping the AST will save a lot of code, but I need help figuring out how to communicate with the CGDebugInfo. Thanks, Amjad From: David Blaikie [mailto:dblaikie at gmail.com] Sent: Tuesday, November 03, 2015 18:46 To: Aboud, Amjad Cc: llvm-dev at lists.llvm.org Subject: Re: [llvm-dev] RFC: Supporting macros in LLVM debug info On Tue, Nov 3, 2015 at 12:16 AM, Aboud, Amjad <amjad.aboud at intel.com<mailto:amjad....

On Fri, Nov 13, 2015 at 2:41 PM, Richard Smith <richard at metafoo.co.uk> wrote: > On Fri, Nov 13, 2015 at 10:21 AM, David Blaikie via cfe-dev < > cfe-dev at lists.llvm.org> wrote: > >> On Mon, Nov 9, 2015 at 4:00 AM, Aboud, Amjad <amjad.aboud at intel.com> >> wrote: >> >>> I found a way to skip representing macros in AST and create them >>> directly in CGDebugInfo through PPCallbacks during preprocessing. >>> >>> To do that, I needed to extend ASTConsumer interface with...

...ch I imagine we would. OK, now I understand what you are aiming for. I really do not favor one on the other. But, can you explain what is the advantage of the parent approach over the children approach? If any, the children approach seems to be the one reduces the LLVM IR size, is not it? Regards, Amjad From: David Blaikie [mailto:dblaikie at gmail.com] Sent: Tuesday, November 03, 2015 18:46 To: Aboud, Amjad Cc: llvm-dev at lists.llvm.org Subject: Re: [llvm-dev] RFC: Supporting macros in LLVM debug info On Tue, Nov 3, 2015 at 12:16 AM, Aboud, Amjad <amjad.aboud at intel.com<mailto:amjad....

...CodeView. When I say that my suggestion is more clean, I was pointing to CodeView support, assuming the changes in LLVM IR/Clang FE indicated in this proposal. Also, it is not that clear from the proposal what will be shared (generic) between Dwarf and CodeView and what will be specific. Regards, Amjad From: mehdi.amini at apple.com [mailto:mehdi.amini at apple.com] Sent: Thursday, March 31, 2016 22:27 To: Aboud, Amjad <amjad.aboud at intel.com> Cc: Eric Christopher <echristo at gmail.com>; Clang Dev <cfe-dev at lists.llvm.org>; llvm-dev <llvm-dev at lists.llvm.org> Subje...

On Mon, Dec 14, 2015 at 7:01 AM, Aboud, Amjad via llvm-dev < llvm-dev at lists.llvm.org> wrote: > Hi, > > I verified that GDB 7.10 does support “DW_AT_abstract_origin” attribute on > “DW_TAG_lexical_block”. > I take it you mean that it does the right thing, finding the direct children of the abstract block when stepping...

...is is supposed to be used and it is not in the example. Also, could we use DIExpansion or some other non macro specific name ? Thanks, Amaury SECHET 2015-11-03 10:34 GMT-08:00 David Blaikie via llvm-dev < llvm-dev at lists.llvm.org>: > > > On Tue, Nov 3, 2015 at 10:19 AM, Aboud, Amjad <amjad.aboud at intel.com> > wrote: > >> > Not necessarily, if we kept the macros in order in the list of macros >> attached to the CU, which I imagine we would. >> >> OK, now I understand what you are aiming for. I really do not favor one >> on the othe...

The split between CodeView and DWARF will happen at the level of type information. So, DIVariable, DISubprogram, DILocation, DILocalScope, etc will all be shared, but records and composite types etc will not. On Thu, Mar 31, 2016 at 3:44 PM, Aboud, Amjad via llvm-dev < llvm-dev at lists.llvm.org> wrote: > Hi Mehdi, > > I understand the reasoning for supporting this proposal independently from > CodeView support. > > However, I do not think that it is needed for supporting CodeView. > > > > When I say that my sug...

...to use the parent chain in addition to the children list, then what extra information it will give us? >Might be good to start with dwarfdump support - seems useful regardless of anything else? I agree, and in fact, I already have this code implemented, will upload it for review soon. Thanks, Amjad From: David Blaikie [mailto:dblaikie at gmail.com] Sent: Tuesday, November 03, 2015 00:32 To: Aboud, Amjad Cc: llvm-dev at lists.llvm.org Subject: Re: [llvm-dev] RFC: Supporting macros in LLVM debug info On Wed, Oct 28, 2015 at 7:56 AM, Aboud, Amjad via llvm-dev <llvm-dev at lists.llvm.org&l...

.... An example for each case. 4. Proposal on how to represent each case in dwarf. 5. Secondary (workaround) proposal which might be needed in the short term until applying a fix in GDB debugger. Please, let me know if you have any comment or feedback on this approach. Thanks, Amjad Motivation Current implementation causes loss of debug info, even when optimizations are disabled. For example: int foo(bool b) { if (b) { typedef int A; class B { public: int x; }; B y; static A z = 0; return y.x + z++; } else { typedef float A;...

...w to represent macro debug info in DWARF 4.0. 3. The suggested design. 4. A full example: Source -> AST -> LLVM IR -> DWARF. Feel free to skip first two parts if you think you know the background. Please, let me know if you have any comment or feedback on this approach. Thanks, Amjad [Background] There are two kind of macro definition: 1. Simple macro definition, e.g. #define M1 Value1 2. Function macro definition, e.g. #define M2(x, y) (x) + (y) Macro scope starts with the "#define" directive and ends with "#undef" directive. GDB supports debugging macr...

...maintainability - there isn't a one true path through things and now is >> scattering more windows knowledge through debug info and lto > >There was never going to be one true way to generate LLVM debug info >for both formats. We need some help from the frontend. I believe that Amjad Aboud has argued several times that there could be one true way to generate LLVM debug info such that both windows and DWARF debug info could be generated from it. I know for a fact that within the Intel Compiler that the FE generates a single set of debug info representation, that then gets trans...

...nd: Extend “X86 Dwarf<->LLVM register mappings” to support “X86 CodeView<->LLVM register mappings” I can think about more differences (gaps) between Dwarf and CodeView that need to be closed, however, it is doable with one uniform (generic) debug info metadata in the LLVM IR. Regards, Amjad From: llvm-dev [mailto:llvm-dev-bounces at lists.llvm.org] On Behalf Of David Blaikie via llvm-dev Sent: Sunday, November 01, 2015 00:20 To: Zachary Turner Cc: llvm-dev; cfe-dev at lists.llvm.org Subject: Re: [llvm-dev] [cfe-dev] RFC: CodeView debug info emission in Clang/LLVM On Sat, Oct 31, 2...

I think it'd be reasonable to at least figure out a good way to do type references consistently across the two schemes, but I'm OK with the idea of having a blob of opaque type information for different debug info formats, created by frontends (& don't mind if the library for building that blob live in LLVM or Clang for now - the DWARF one at least would probably live in LLVM

Hi Aboud, > On Mar 31, 2016, at 11:06 AM, Aboud, Amjad via cfe-dev <cfe-dev at lists.llvm.org> wrote: > > Hi Eric, > I can understand the need for improving the current design of debug info representation and emission in LLVM. > However, let’s not forget that the motivation was and still to support CodeView debug info emission. Well...

How do you keep oggenc open long enough to even USE it?!?!?!?!?! Whenever I tell the computer to open the file, it says [Process Completed] and [logout]. What is going on?

...e are planning to implement quotas for end users having limit on home directories 10GB. Is using "lquota" the only way or can we also use traditional Linux method of adding "usrquota" in /etc/fstab? If both methods can be used what are pros and cons of each method? Sincerely, Amjad _______________________________________________ Lustre-discuss mailing list Lustre-discuss-aLEFhgZF4x6X6Mz3xDxJMA@public.gmane.org http://lists.lustre.org/mailman/listinfo/lustre-discuss