public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "danglin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/55627] [4.8 Regression] FAIL: g++.dg/bprob/g++-bprob-1.C execution,    -Os  -fprofile-arcs
Date: Sun, 09 Dec 2012 15:59:00 -0000	[thread overview]
Message-ID: <bug-55627-4-k4Y53SN3MZ@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-55627-4@http.gcc.gnu.org/bugzilla/>


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

--- Comment #1 from John David Anglin <danglin at gcc dot gnu.org> 2012-12-09 15:59:24 UTC ---
(gdb) p for_val2
$2 = 6
(gdb) p goto_val
$3 = 11
(gdb) p for_val1
$4 = 12
(gdb) p for_val2
$5 = 6
(gdb) p goto_val
$6 = 11
(gdb) p ifelse_val1
$7 = 31
(gdb) p ifelse_val2
$8 = 23
(gdb) p ifelse_val3
$9 = 246
(gdb) p switch_val
$10 = 55

for_val2 and goto_val are wrong.


  reply	other threads:[~2012-12-09 15:59 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-09 15:51 [Bug rtl-optimization/55627] New: " danglin at gcc dot gnu.org
2012-12-09 15:59 ` danglin at gcc dot gnu.org [this message]
2012-12-11 10:43 ` [Bug rtl-optimization/55627] " rguenth at gcc dot gnu.org
2013-01-07 15:29 ` rguenth at gcc dot gnu.org
2013-01-08  1:28 ` danglin 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-55627-4-k4Y53SN3MZ@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).