Re: [Dwarf-discuss] Seeking a test program with a >4GB .debug_info section

2023-04-24 Thread David Blaikie via Dwarf-discuss
On Fri, Apr 21, 2023 at 2:16 PM John DelSignore wrote: > > On 4/21/23 16:36, David Blaikie wrote: > > On Fri, Apr 21, 2023 at 12:44 PM John DelSignore > wrote: > >> Well, it took a long time to compile 5 CUs that contained your test code, >> and things were looking promising, but the link failed

Re: [Dwarf-discuss] Seeking a test program with a >4GB .debug_info section

2023-04-21 Thread John DelSignore via Dwarf-discuss
On 4/21/23 16:36, David Blaikie wrote: On Fri, Apr 21, 2023 at 12:44 PM John DelSignore mailto:jdelsign...@perforce.com>> wrote: Well, it took a long time to compile 5 CUs that contained your test code, and things were looking promising, but the link failed: rocm2 42 04/21 15:14 /build/jdelsig

Re: [Dwarf-discuss] Seeking a test program with a >4GB .debug_info section

2023-04-21 Thread David Blaikie via Dwarf-discuss
On Fri, Apr 21, 2023 at 12:44 PM John DelSignore wrote: > Well, it took a long time to compile 5 CUs that contained your test code, > and things were looking promising, but the link failed: > > rocm2 42 04/21 15:14 /build/jdelsign/fatty % make > g++ -g -c fatty4.cxx -o fatty4.o > g++ -g -c fatty5

Re: [Dwarf-discuss] Seeking a test program with a >4GB .debug_info section

2023-04-21 Thread John DelSignore via Dwarf-discuss
Well, it took a long time to compile 5 CUs that contained your test code, and things were looking promising, but the link failed: rocm2 42 04/21 15:14 /build/jdelsign/fatty % make g++ -g -c fatty4.cxx -o fatty4.o g++ -g -c fatty5.cxx -o fatty5.o g++ -g -o fatty fatty.o fatty2.o fatty3.o fatty4.o

Re: [Dwarf-discuss] Seeking a test program with a >4GB .debug_info section

2023-04-21 Thread John DelSignore via Dwarf-discuss
Thanks David, this is useful. I'll see what I can cobble together. Cheers, John D. On 4/20/23 21:58, David Blaikie wrote: Oh, and I guess you could always make something even more artificial by hand - if you compile some random code with -g to assembly, you could then just pad out a .debug_info

Re: [Dwarf-discuss] Seeking a test program with a >4GB .debug_info section

2023-04-20 Thread David Blaikie via Dwarf-discuss
Oh, and I guess you could always make something even more artificial by hand - if you compile some random code with -g to assembly, you could then just pad out a .debug_info contribution with lots of zeros (there are some assembly directives for that, I think, but don't know assembly that well off

Re: [Dwarf-discuss] Seeking a test program with a >4GB .debug_info section

2023-04-20 Thread David Blaikie via Dwarf-discuss
I /believe/ that Chromium (maybe specifically on ARM? not sure) may have hit/had problems with the 4GB limit - probably trivially if you build with clang but pass `-fstandalone-debug` which disables many type reduction/deduplication strategies. If you want something more standalone... this: #def