public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/103329] [11/12 Regression] Code divergence in debug info with -fdump-tree-original since r11-291-g0f50f6daa140186a Date: Fri, 19 Nov 2021 13:00:55 +0000 [thread overview] Message-ID: <bug-103329-4-v3u6S3jwVD@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-103329-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103329 --- Comment #2 from Richard Biener <rguenth at gcc dot gnu.org> --- In the -fdump-tree-original=/dev/null case we have extra <1><107>: Abbrev Number: 3 (DW_TAG_structure_type) <108> DW_AT_name : (indirect string, offset: 0xb8): __is_integer<int> <10c> DW_AT_byte_size : 1 <10c> DW_AT_decl_file : 1 <10c> DW_AT_decl_line : 2 <10d> DW_AT_decl_column : 8 <10e> DW_AT_sibling : <0x124> <2><112>: Abbrev Number: 22 (DW_TAG_enumeration_type) <113> DW_AT_encoding : 7 (unsigned) <114> DW_AT_byte_size : 4 <115> DW_AT_type : <0x57> <119> DW_AT_decl_file : 1 <11a> DW_AT_decl_line : 3 <11b> DW_AT_decl_column : 8 <3><11c>: Abbrev Number: 23 (DW_TAG_enumerator) <11d> DW_AT_name : (indirect string, offset: 0x24a): __value <121> DW_AT_const_value : 0 <3><122>: Abbrev Number: 0 <2><123>: Abbrev Number: 0
next prev parent reply other threads:[~2021-11-19 13:00 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-11-19 10:40 [Bug c++/103329] New: " marxin at gcc dot gnu.org 2021-11-19 10:41 ` [Bug c++/103329] " marxin at gcc dot gnu.org 2021-11-19 13:00 ` rguenth at gcc dot gnu.org [this message] 2021-11-22 17:40 ` jakub at gcc dot gnu.org 2021-12-31 15:56 ` jakub at gcc dot gnu.org 2022-01-18 14:27 ` rguenth at gcc dot gnu.org 2022-04-05 16:46 ` jason at gcc dot gnu.org 2022-04-05 19:16 ` jason at gcc dot gnu.org 2022-04-05 19:16 ` jason at gcc dot gnu.org 2022-04-06 8:47 ` marxin at gcc dot gnu.org
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-103329-4-v3u6S3jwVD@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).