public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug debug/65779] [5/6 Regression] undefined local symbol on powerpc [regression]
Date: Fri, 17 Apr 2015 07:28:00 -0000	[thread overview]
Message-ID: <bug-65779-4-4XFFkU6Bh4@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-65779-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #6 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
(In reply to Alan Modra from comment #4)
> Created attachment 35342 [details]
> prototype patch
> 
> This seems to cure the testcase.  I haven't bootstrapped it, and it probably
> isn't ideal since I haven't poked at debug insns a lot..
> Still, it points out where the problem is, in move_insn_for_shrink_wrap.

Can't you use DF infrastructure for that (before actually moving the insn)?
I think pro_and_epilogue pass doesn't compute DF_DU_CHAINs, but perhaps
something along the lines of DCE reset_unmarked_insns_debug_uses?
I.e. not perform it at all if !MAY_HAVE_DEBUG_INSNS, and use DF infrastructure
to find out if the debug insn references the register.  Of course, unlike DCE,
we aren't looking at debug instructions referencing unmarked insns, but debug
instructions referencing a particular hard register.  Note that
live_edge_for_reg is called multiple times and thus could move across more than
one basic block, so perhaps you'd need to remember the sequence of basic blocks
to scan during the
  /* At this point we are committed to moving INSN, but let's try to
     move it as far as we can.  */
loop.


  parent reply	other threads:[~2015-04-17  7:28 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-15 21:45 [Bug target/65779] New: undefined local symbol on powerpc joel at gcc dot gnu.org
2015-04-16  7:39 ` [Bug target/65779] [5 Regression] undefined local symbol on powerpc [regression] rguenth at gcc dot gnu.org
2015-04-16 14:00 ` [Bug target/65779] [5/6 " jakub at gcc dot gnu.org
2015-04-17  1:51 ` amodra at gmail dot com
2015-04-17  2:13 ` amodra at gmail dot com
2015-04-17  5:26 ` [Bug debug/65779] " amodra at gmail dot com
2015-04-17  7:28 ` jakub at gcc dot gnu.org [this message]
2015-04-22 11:58 ` jakub at gcc dot gnu.org
2015-06-30 10:20 ` rguenth at gcc dot gnu.org
2015-07-16  9:16 ` rguenth at gcc dot gnu.org
2015-10-08 23:55 ` pangbw at gmail dot com
2015-10-09 23:47 ` pangbw at gmail dot com
2015-10-15 14:31 ` segher 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-65779-4-4XFFkU6Bh4@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).