search for: ikudrin

Displaying 20 results from an estimated 23 matches for "ikudrin".

Did you mean: kudrin
2017 Nov 10
2
[RFC] Making .eh_frame more linker-friendly
...It will also improve eh_frame_hdr build time because you don’t spend time on parsing garbage. However a linker will have to have two versions of GC: one with parsing eh_frames and another without parsing. There can be input object files where .eh_frame is not split. -Evgeny From: Igor Kudrin <ikudrin at accesssoftek.com> Date: Friday, 10 November 2017 at 12:23 To: Evgeny Astigeevich <Evgeny.Astigeevich at arm.com> Cc: nd <nd at arm.com>, "llvm-dev at lists.llvm.org" <llvm-dev at lists.llvm.org> Subject: Re: [llvm-dev] [RFC] Making .eh_frame more linker-friendly...
2017 Nov 10
2
[RFC] Making .eh_frame more linker-friendly
...or two? What do you mean “one place or two”? If .eh_frame_hdr is not created a linker does not need to parse .eh_frame sections. It simply merges them into one section. The format of .eh_frame allows to do this without parsing .eh_frame sections. Thanks, Evgeny Astigeevich From: Igor Kudrin <ikudrin.dev at gmail.com> Date: Thursday, 9 November 2017 at 11:29 To: Rui Ueyama <ruiu at google.com>, Evgeny Astigeevich <Evgeny.Astigeevich at arm.com> Cc: "llvm-dev at lists.llvm.org" <llvm-dev at lists.llvm.org>, nd <nd at arm.com> Subject: Re: [llvm-dev] [RFC] Mak...
2016 Apr 19
2
Possible UB in reading coverage mapping with compressed function names
Hi David, Vedant, It looks like we might have UB somewhere connected with reading coverage mapping serialized in v2 format (with compressed function names). I committed my patch, r266436, using the current format for .covmapping file, and then buildbots complained about it: * http://lab.llvm.org:8011/builders/sanitizer-x86_64-linux-fast/builds/11935/steps/check-llvm%20ubsan/logs/stdio *
2020 Nov 17
5
[LLD] Support DWARF64, debug_info "sorting"
On Mon, Nov 16, 2020 at 10:42 PM Igor Kudrin <ikudrin at accesssoftek.com> wrote: > > On 14.11.2020 3:42, Fāng-ruì Sòng wrote: > > For .debug_* in object files: > > > > DWARF32 -> SHT_PROGBITS (unchanged) > > DWARF64 -> SHT_DWARF64 or SHT_GNU_DWARF64 > > > > In LLD, we will need to allow mixed SHT_PRO...
2020 Nov 18
2
[LLD] Support DWARF64, debug_info "sorting"
On 2020-11-17, Igor Kudrin wrote: > >On 17.11.2020 14:05, Fāng-ruì Sòng wrote: >>On Mon, Nov 16, 2020 at 10:42 PM Igor Kudrin <ikudrin at accesssoftek.com> wrote: >>> >>>On 14.11.2020 3:42, Fāng-ruì Sòng wrote: >>>>For .debug_* in object files: >>>> >>>>DWARF32 -> SHT_PROGBITS (unchanged) >>>>DWARF64 -> SHT_DWARF64 or SHT_GNU_DWARF64 >>>> >&g...
2020 Nov 18
0
[LLD] Support DWARF64, debug_info "sorting"
...provide this information, then it's a current behavior which also adheres to DWARF spec that says if DWARF32 and DWARF64 the onus is on the user. Alex ________________________________ From: Fāng-ruì Sòng <maskray at google.com> Sent: Tuesday, November 17, 2020 4:49 PM To: Igor Kudrin <ikudrin at accesssoftek.com> Cc: David Blaikie <dblaikie at gmail.com>; Wenlei He <wenlei at fb.com>; Alexander Yermolovich <ayermolo at fb.com>; llvm-dev at lists.llvm.org <llvm-dev at lists.llvm.org>; Robinson, Paul <paul.robinson at sony.com>; James Henderson <jh7370....
2020 Apr 28
2
[RFC] DWARF Version 6 Proposal For Heterogeneous Debugging
Hi Scott, It's possible they've missed it, so I've explicitly CC'ed a number of the usual DWARF suspects, at least some of whom are on the standards committee. I don't have anything specific to add myself. James On Mon, 27 Apr 2020 at 15:25, via llvm-dev <llvm-dev at lists.llvm.org> wrote: > I don't know what an acceptable ping rate on an RFC is, but I also
2020 Nov 13
3
[LLD] Support DWARF64, debug_info "sorting"
...nt: Thursday, November 12, 2020 2:20 AM To: Fangrui Song <maskray at google.com> Cc: Alexander Yermolovich <ayermolo at fb.com>; Robinson, Paul <paul.robinson at sony.com>; David Blaikie <dblaikie at gmail.com>; Eric Christopher <echristo at gmail.com>; Igor Kudrin <ikudrin at accesssoftek.com>; llvm-dev at lists.llvm.org <llvm-dev at lists.llvm.org> Subject: Re: [llvm-dev] [LLD] Support DWARF64, debug_info "sorting" On Thu, 12 Nov 2020 at 02:10, Fangrui Song <maskray at google.com<mailto:maskray at google.com>> wrote: On 2020-11-12,...
2020 Nov 11
1
[LLD] Support DWARF64, debug_info "sorting"
Thanks Alexander for bringing this up! > The major drawback in sorting, is the need to parse DWARF, even a little bit > of it (only the first 4 bytes of a section to tell which version it is - first 12 if you > want to be able to jump over contributions and check /all/ contributions > coming from a given input object file (it might contain a combination of > DWARFv4 and DWARFv5)
2020 Nov 17
0
[EXTERNAL] Re: [LLD] Support DWARF64, debug_info "sorting"
On 17.11.2020 14:05, Fāng-ruì Sòng wrote: > On Mon, Nov 16, 2020 at 10:42 PM Igor Kudrin <ikudrin at accesssoftek.com> wrote: >> >> On 14.11.2020 3:42, Fāng-ruì Sòng wrote: >>> For .debug_* in object files: >>> >>> DWARF32 -> SHT_PROGBITS (unchanged) >>> DWARF64 -> SHT_DWARF64 or SHT_GNU_DWARF64 >>> >>> In LLD, we will n...
2020 Nov 17
0
[LLD] Support DWARF64, debug_info "sorting"
...Cc: David Blaikie <dblaikie at gmail.com>; Wenlei He <wenlei at fb.com>; llvm- > dev at lists.llvm.org; Robinson, Paul <paul.robinson at sony.com>; James > Henderson <jh7370.2008 at my.bristol.ac.uk>; Eric Christopher > <echristo at gmail.com>; Igor Kudrin <ikudrin at accesssoftek.com> > Subject: Re: [llvm-dev] [LLD] Support DWARF64, debug_info "sorting" > > On 2020-11-14, Alexander Yermolovich wrote: > >Thanks for doing a diff and asking in other groups. > > > >So if I understand your concern with using first reloc as...
2020 Nov 18
2
[LLD] Support DWARF64, debug_info "sorting"
...ing standards. The committee may also have some thoughts on how tools are expected to work with DWARF64 and DWARF32 mixtures. > > James > > On Tue, 17 Nov 2020 at 07:06, Fāng-ruì Sòng <maskray at google.com> wrote: >> >> On Mon, Nov 16, 2020 at 10:42 PM Igor Kudrin <ikudrin at accesssoftek.com> wrote: >> > >> > On 14.11.2020 3:42, Fāng-ruì Sòng wrote: >> > > For .debug_* in object files: >> > > >> > > DWARF32 -> SHT_PROGBITS (unchanged) >> > > DWARF64 -> SHT_DWARF64 or SHT_GNU_DWARF64 >>...
2020 Nov 19
1
[LLD] Support DWARF64, debug_info "sorting"
On 19.11.2020 03:21, Cary Coutant wrote: >>> If the .debug_str section *by itself* exceeds 4GB, then yes any string >>> with a 32-bit reference to it must be in the first 4GB. Strings that >>> have only 64-bit references to them can be sorted to the end of the >>> section, if necessary. I wouldn't think anyone guarantees or cares >>> about the
2020 Nov 17
0
[LLD] Support DWARF64, debug_info "sorting"
...retroactively applied to existing standards. The committee may also have some thoughts on how tools are expected to work with DWARF64 and DWARF32 mixtures. James On Tue, 17 Nov 2020 at 07:06, Fāng-ruì Sòng <maskray at google.com> wrote: > On Mon, Nov 16, 2020 at 10:42 PM Igor Kudrin <ikudrin at accesssoftek.com> > wrote: > > > > On 14.11.2020 3:42, Fāng-ruì Sòng wrote: > > > For .debug_* in object files: > > > > > > DWARF32 -> SHT_PROGBITS (unchanged) > > > DWARF64 -> SHT_DWARF64 or SHT_GNU_DWARF64 > > > > > &gt...
2020 Nov 13
0
[LLD] Support DWARF64, debug_info "sorting"
...y, November 12, 2020 2:20 AM > To: Fangrui Song <maskray at google.com> > Cc: Alexander Yermolovich <ayermolo at fb.com>; Robinson, Paul < paul.robinson at sony.com>; David Blaikie <dblaikie at gmail.com>; Eric Christopher <echristo at gmail.com>; Igor Kudrin <ikudrin at accesssoftek.com>; llvm-dev at lists.llvm.org <llvm-dev at lists.llvm.org> > Subject: Re: [llvm-dev] [LLD] Support DWARF64, debug_info "sorting" I probably should have mentioned that I had started a prototype:) (And I realized that I could use firstRelocation instead of de...
2020 Nov 18
0
[LLD] Support DWARF64, debug_info "sorting"
...so have some thoughts on how tools are expected to work > with DWARF64 and DWARF32 mixtures. > > > > James > > > > On Tue, 17 Nov 2020 at 07:06, Fāng-ruì Sòng <maskray at google.com> wrote: > >> > >> On Mon, Nov 16, 2020 at 10:42 PM Igor Kudrin <ikudrin at accesssoftek.com> > wrote: > >> > > >> > On 14.11.2020 3:42, Fāng-ruì Sòng wrote: > >> > > For .debug_* in object files: > >> > > > >> > > DWARF32 -> SHT_PROGBITS (unchanged) > >> > > DWARF64 -> SHT_D...
2020 Nov 17
2
[LLD] Support DWARF64, debug_info "sorting"
On 2020-11-14, Alexander Yermolovich wrote: >Thanks for doing a diff and asking in other groups. > >So if I understand your concern with using first reloc as it relates to .debug_str. > >In DWARF4 for .debug_str is referenced from .debug_info, .debug_type using DW_FORM_strp. For DWARF32 it's 32bit unsigned, for DWARF64 it's 64bit unsigned. So in relocation section for some
2018 Feb 27
1
RFC: LLVM - lld - Add visual studio compatible diagnostics output to lld
Hi, We would like to see that change, too, especially for lld/ELF. Chris, do you have a patch or just looking for help? Best Regards, Igor Kudrin C++ Developer, Access Softek, Inc. ________________________________ From: llvm-dev <llvm-dev-bounces at lists.llvm.org> on behalf of Rui Ueyama via llvm-dev <llvm-dev at lists.llvm.org> Sent: Friday, February 23, 2018 6:37 AM To: Chris
2020 Nov 14
0
[LLD] Support DWARF64, debug_info "sorting"
...at fb.com>; Alexander Yermolovich <ayermolo at fb.com>; llvm-dev at lists.llvm.org <llvm-dev at lists.llvm.org>; Robinson, Paul <paul.robinson at sony.com>; James Henderson <jh7370.2008 at my.bristol.ac.uk>; Eric Christopher <echristo at gmail.com>; Igor Kudrin <ikudrin at accesssoftek.com> Subject: Re: [llvm-dev] [LLD] Support DWARF64, debug_info "sorting" On Fri, Nov 13, 2020 at 11:29 AM David Blaikie <dblaikie at gmail.com> wrote: > > On Fri, Nov 13, 2020 at 11:24 AM Fāng-ruì Sòng <maskray at google.com> wrote: > > > &gt...
2020 Nov 13
4
[LLD] Support DWARF64, debug_info "sorting"
On Fri, Nov 13, 2020 at 11:29 AM David Blaikie <dblaikie at gmail.com> wrote: > > On Fri, Nov 13, 2020 at 11:24 AM Fāng-ruì Sòng <maskray at google.com> wrote: > > > > On Fri, Nov 13, 2020 at 11:17 AM David Blaikie <dblaikie at gmail.com> wrote: > > > > > > On Fri, Nov 13, 2020 at 11:05 AM Fāng-ruì Sòng <maskray at google.com> wrote: >