public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Alan Modra <amodra@gmail.com>
To: Andreas Schwab <schwab@linux-m68k.org>
Cc: Bernd Schmidt <bschmidt@redhat.com>, gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] PR69195, Reload confused by invalid reg equivs
Date: Fri, 11 Mar 2016 23:13:00 -0000	[thread overview]
Message-ID: <20160311231350.GC16812@bubble.grove.modra.org> (raw)
In-Reply-To: <20160311221624.GB16812@bubble.grove.modra.org>

The underlying problem happens somewhere in tree-ssa-dse.c.  So we get
an indirect jump to a random location instead of a jump to 0.

pr58164.c.035t.mergephi1
;; Function foo (foo, funcdef_no=0, decl_uid=1389, cgraph_uid=0, symbol_order=0)

foo ()
{
  int x;

  <bb 2>:
  x = 0;
  goto &x;

}

pr58164.c.036t.dse1
;; Function foo (foo, funcdef_no=0, decl_uid=1389, cgraph_uid=0, symbol_order=0)

  Deleted dead store 'x = 0;
'
foo ()
{
  int x;

  <bb 2>:
  goto &x;

}

-- 
Alan Modra
Australia Development Lab, IBM

  reply	other threads:[~2016-03-11 23:13 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-04 14:54 [RFC] " Alan Modra
2016-03-04 17:40 ` Bernd Schmidt
2016-03-07 14:47   ` Alan Modra
2016-03-10  9:18     ` [PATCH] " Alan Modra
2016-03-10  9:48       ` Bernd Schmidt
2016-03-11 20:40       ` Andreas Schwab
2016-03-11 22:16         ` Alan Modra
2016-03-11 23:13           ` Alan Modra [this message]
2016-03-12  7:58             ` Jakub Jelinek
2016-03-12  8:26               ` Jeff Law
2016-03-12  9:07                 ` Alan Modra
2016-03-12  9:29                   ` Jakub Jelinek
2016-03-12 11:10                     ` Richard Biener
2016-03-12 17:07                       ` Jeff Law
2016-03-14  9:56                         ` Richard Biener
2016-03-14 19:00                           ` Jeff Law
2016-03-15  2:27                             ` Alan Modra
2016-03-15 12:17                               ` Bernd Schmidt

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=20160311231350.GC16812@bubble.grove.modra.org \
    --to=amodra@gmail.com \
    --cc=bschmidt@redhat.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=schwab@linux-m68k.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).