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 debug/101473] debug_line info depends on toolchain path
Date: Mon, 19 Jul 2021 14:06:49 +0000	[thread overview]
Message-ID: <bug-101473-4-KMDEWc2CQQ@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-101473-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101473

Richard Biener <rguenth at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Summary|LTO makes debug info depend |debug_line info depends on
                   |on toolchain path           |toolchain path
                 CC|                            |jakub at gcc dot gnu.org
          Component|lto                         |debug

--- Comment #7 from Richard Biener <rguenth at gcc dot gnu.org> ---
Easily pulled in via

typedef __SIZE_TYPE__ size_t;

in said include.  Maybe expanding the list of basetypes could help here...

 <1><2e>: Abbrev Number: 4 (DW_TAG_typedef)
    <2f>   DW_AT_name        : (indirect string, offset: 0x2f): size_t
    <33>   DW_AT_decl_file   : 2
    <34>   DW_AT_decl_line   : 209
    <35>   DW_AT_decl_column : 23
    <36>   DW_AT_type        : <0x3a>
 <1><3a>: Abbrev Number: 2 (DW_TAG_base_type)
    <3b>   DW_AT_byte_size   : 8
    <3c>   DW_AT_encoding    : 7        (unsigned)
    <3d>   DW_AT_name        : (indirect string, offset: 0x1ab): long unsigned
int

note there are other headers like omp.h which are also in install path
dependent directories.

  parent reply	other threads:[~2021-07-19 14:06 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-16 14:11 [Bug lto/101473] New: LTO makes debug info depend " tonyb at cybernetics dot com
2021-07-19  6:18 ` [Bug lto/101473] " rguenth at gcc dot gnu.org
2021-07-19  7:53 ` rguenth at gcc dot gnu.org
2021-07-19 13:12 ` tonyb at cybernetics dot com
2021-07-19 13:15 ` tonyb at cybernetics dot com
2021-07-19 13:22 ` rguenth at gcc dot gnu.org
2021-07-19 13:28 ` tonyb at cybernetics dot com
2021-07-19 14:06 ` rguenth at gcc dot gnu.org [this message]
2021-07-19 14:08 ` [Bug debug/101473] debug_line info depends " rguenth at gcc dot gnu.org
2021-07-19 14:10 ` rguenth at gcc dot gnu.org
2021-07-19 14:17 ` rguenth at gcc dot gnu.org
2021-07-19 14:58 ` tonyb at cybernetics dot com
2021-07-19 19:24 ` tonyb at cybernetics dot com
2021-07-20  7:10 ` rguenther at suse dot de
2021-07-20  9:06 ` rguenth at gcc dot gnu.org
2021-07-20 10:50 ` cvs-commit at gcc dot gnu.org
2021-07-20 10:51 ` rguenth at gcc dot gnu.org
2021-07-20 17:58 ` tonyb at cybernetics dot com
2021-07-20 18:02 ` tonyb at cybernetics dot com
2021-07-21 10:34 ` rguenth at gcc dot gnu.org
2021-07-21 11:04 ` jakub at gcc dot gnu.org
2021-07-21 13:40 ` tonyb at cybernetics dot com
2021-11-09 14:34 ` rguenth 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-101473-4-KMDEWc2CQQ@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: link
Be 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).