https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116462
Kewen Lin <linkw at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target Milestone|--- |15.0
Ever confirmed|0 |1
Assignee|unassigned at gcc dot gnu.org |bernd.edlinger at
hotmail dot de
Last reconfirmed| |2024-08-23
CC| |linkw at gcc dot gnu.org
Status|UNCONFIRMED |ASSIGNED
--- Comment #3 from Kewen Lin <linkw at gcc dot gnu.org> ---
(In reply to Bernd Edlinger from comment #2)
> no forget it, this might make arm unhappy...
>
> lets try this instead:
>
> --- a/gcc/testsuite/gcc.dg/debug/dwarf2/inline7.c
> +++ b/gcc/testsuite/gcc.dg/debug/dwarf2/inline7.c
> @@ -1,9 +1,9 @@
> -/* Verify that both inline instances have a DW_AT_ranges but
> - no extra DW_TAG_lexical_block. */
> +/* Verify that at least one of both inline instances have
> + a DW_AT_ranges but no extra DW_TAG_lexical_block. */
> /* { dg-options "-O -gdwarf -dA" } */
> /* { dg-do compile } */
> /* { dg-final { scan-assembler-times "\\(DIE \\(\[^\n\]*\\)
> DW_TAG_inlined_subroutine" 2 } } */
> -/* { dg-final { scan-assembler-times " DW_AT_ranges" 2 } } */
> +/* { dg-final { scan-assembler " DW_AT_ranges" } } */
> /* { dg-final { scan-assembler-times "\\(DIE \\(\[^\n\]*\\)
> DW_TAG_lexical_block" 0 } } */
>
> static int foo (int i)
This works well on Power, thanks for fixing! I'm curious why the DW_AT_ranges
on Power is different from what's on most others, does the information depend
on some specific handling in port?
