public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug other/42715] [4.5 Regression] output_operand: invalid expression as operand
Date: Wed, 13 Jan 2010 12:10:00 -0000	[thread overview]
Message-ID: <20100113120956.30626.qmail@sourceware.org> (raw)
In-Reply-To: <bug-42715-11764@http.gcc.gnu.org/bugzilla/>



------- Comment #5 from jakub at gcc dot gnu dot org  2010-01-13 12:09 -------
Looks like some var-tracking bug.  We have:
(insn:TI 108 37 38 3 (set (reg/f:SI 2 cx [93]) (const:SI (unspec:SI
[(symbol_ref:SI ("v1") [flags 0x2]  <var_decl 0x7fc316f38000 v1>)] 1))) 247
{*lea_1} (expr_list:REG_EQUAL (const:SI (unspec:SI [(symbol_ref:SI ("v1")
[flags 0x2]  <var_decl 0x7fc316f38000 v1>)] 1)) (nil)))
and then:
(insn:TI 57 56 59 18 pr42715.i:12 (parallel [(set (reg:SI 2 cx [orig:86 v ]
[86]) (asm_operands/v:SI ("") ("=r") 0 []...)
(debug_insn 59 57 60 18 pr42715.i:12 (var_location:SI v (reg:SI 2 cx [orig:86 v
] [86])) -1 (nil))
...
(call_insn:TI 64 63 190 18 pr42715.i:20 (set (reg:SI 0 ax) ...)
(jump_insn 190 64 191 18 (set (pc) (label_ref 65)) -1 (nil) -> 65)
with no labels in between 57 and 190.  But var-tracking somehow manages to
resurrect the unspec value of cx that cx obviously doesn't have after the call
(where it has undefined value).  Alex, can you please have a look?


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42715


  parent reply	other threads:[~2010-01-13 12:10 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-12 17:07 [Bug other/42715] New: " doko at ubuntu dot com
2010-01-12 17:07 ` [Bug other/42715] " doko at ubuntu dot com
2010-01-12 23:35 ` hjl dot tools at gmail dot com
2010-01-13  9:52 ` rguenth at gcc dot gnu dot org
2010-01-13 11:12 ` rguenth at gcc dot gnu dot org
2010-01-13 11:57 ` jakub at gcc dot gnu dot org
2010-01-13 12:10 ` jakub at gcc dot gnu dot org [this message]
2010-01-14 16:40 ` rguenth at gcc dot gnu dot org
2010-01-19  8:45 ` aoliva at gcc dot gnu dot org
2010-01-21  0:43 ` jakub at gcc dot gnu dot org
2010-01-22 17:03 ` jakub at gcc dot gnu dot org
2010-02-07  4:48 ` hjl at gcc dot gnu dot 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=20100113120956.30626.qmail@sourceware.org \
    --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).