search for: aboud

...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 scope of explicit casting type does not seem correct Under what conditions do we produce a subpro...

...") 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 scope of explicit casting type does not seem correct Yep, seems fine/reasonable to me. The pointe...

...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> Subject: Re: [cfe-dev] [llvm-dev] RFC: Up front type information generation in clang and llvm Hi Aboud, On Mar 31, 2...

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: > > > &gt...

Hi, I am wondering if this behavior of creating debug info is correct. A type in compile unit entry is pointing to a type under subprogram entry?! This is the root cause of https://llvm.org/bugs/show_bug.cgi?id=27579 0x0000000b: DW_TAG_compile_unit [1] * 0x00000026: DW_TAG_pointer_type [2] DW_AT_type [DW_FORM_ref4] (cu + 0x002c => {0x0000002c})

...hich 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.aboud at intel.com>> wrote: > Do we really need to touch the AST? Or would it be reasonable...

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

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

...any way to speed this up? The one idea I have is having R call a C or Perl routine, reading the file in that language, converting the data in to R objects, then sending them back into R. This is more work that I want to do, however, in loading Rdata files. Any ideas would be appreciated. Ramzi Aboud University of Rochester ____________________________________________________________________________________ Need Mail bonding?

...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.aboud at intel.com>> wrote: > Do we really need to touch the AST? Or would it be reasonable...

...how this 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 t...

...? >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<mailto:llvm-dev at lists.llvm.org>> wrote: Hi, I would like to implement macro debug info sup...

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

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

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

Hi, I would like to implement a fix to how LLVM handles/creates debug info for entities declared inside a basic block. Below you will find 5 parts: 1. Motivation for this fix. 2. Background explaining the cases that need to be fixed. 3. An example for each case. 4. Proposal on how to represent each case in dwarf. 5. Secondary (workaround) proposal which might be

...eadline for new memberships and renewals > finishes in a couple of weeks. Original email follows. > > Thanks for your attention. I don't know if I'm the only one affected by this issue, but I've just received today two months of e-mails from x.org, including all the reminders aboud membership renewal and election nomination period. This isn't the first time this happens, and the last time I was told there was no automated process to quick the mail queues when errors happen, making mails pile up forever on x.org's side until someone handles it manually. This is somethi...

Hi, I would like to implement macro debug info support in LLVM. Below you will find 4 parts: 1. Background on what does it mean to debug macros. 2. A brief explanation on how 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.

The 2023 X.Org Foundation elections are rapidly approaching. We will be forwarding the election schedule and nominating process to the membership shortly. Please note that only current members can vote in the upcoming election, and that the deadline for new memberships or renewals to vote in the upcoming election is 26 March 2023 at 23:59 UTC. If you are interested in joining the X.Org

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