public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "hubicka at ucw dot cz" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/65797] [5.0 regression] IPA ICF causes function to be emitted with no debug line info
Date: Fri, 17 Apr 2015 22:39:00 -0000	[thread overview]
Message-ID: <bug-65797-4-KkhoiYdUzC@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-65797-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #3 from Jan Hubicka <hubicka at ucw dot cz> ---
Hi,
the ICF wrapper are created same way as thunks (by expand_thunk) which probably
suppress debug info because we do not want to see it for thunks. I suppose it
is:
DECL_IGNORED_P (thunk_fndecl) = 1
I suppose we can add a parameter that will enable debug info production and
pass it
as true via the create_wrapper path (can't hack it right now as I am on a trip
in China)
I am adding Martin to CC.

In many cases we however create a wrapper where keeping function is backtrace
is even harder. If go needs functions in backtrace even in this case (when they
are not exported nor have address taken) perhaps we have to disable ICF?
We may add a way to disable ICF per function basis.

Honza


  parent reply	other threads:[~2015-04-17 22:39 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-17 20:43 [Bug tree-optimization/65797] New: " ian at airs dot com
2015-04-17 21:29 ` [Bug tree-optimization/65797] " ian at gcc dot gnu.org
2015-04-17 21:29 ` ian at gcc dot gnu.org
2015-04-17 22:39 ` hubicka at ucw dot cz [this message]
2015-04-17 23:00 ` [Bug tree-optimization/65797] [5 " ian at airs dot com
2015-04-17 23:09 ` hubicka at ucw dot cz
2015-04-17 23:12 ` hubicka at ucw dot cz
2015-04-17 23:15 ` ian at airs dot com
2015-04-18  2:48 ` hubicka at ucw dot cz
2015-04-20  8:26 ` rguenth at gcc dot gnu.org
2015-06-30 10:22 ` [Bug ipa/65797] [5/6 " rguenth at gcc dot gnu.org
2015-07-16  9:11 ` rguenth at gcc dot gnu.org
2021-05-14  9:47 ` [Bug ipa/65797] [9/10/11/12 " jakub at gcc dot gnu.org
2021-06-01  8:06 ` rguenth at gcc dot gnu.org
2022-05-27  9:35 ` [Bug ipa/65797] [10/11/12/13 " rguenth at gcc dot gnu.org
2022-06-28 10:31 ` jakub at gcc dot gnu.org
2023-07-07 10:30 ` [Bug ipa/65797] [11/12/13/14 " 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-65797-4-KkhoiYdUzC@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).