public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "wschmidt at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/66868] [5/6 Regression] wrong code generated with -O3 (dead code removal?)
Date: Wed, 22 Jul 2015 13:54:00 -0000	[thread overview]
Message-ID: <bug-66868-4-8dumlOSJ3j@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-66868-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #5 from Bill Schmidt <wschmidt at gcc dot gnu.org> ---
Using current trunk, I compared the 193t.optimized dumps for the original
cdrom.ii attachment and for the same attachment modified to add the debug
output statement from the end of comment 2.  Other than the added statements
for the debug output, there don't appear to be any changes.  This bug is marked
as 5.1/6 regression -- are you certain that it regresses on trunk?  Will check
5.1 the same way.


  parent reply	other threads:[~2015-07-22 13:54 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-14 12:06 [Bug tree-optimization/66868] New: " doko at gcc dot gnu.org
2015-07-14 12:25 ` [Bug tree-optimization/66868] " trippels at gcc dot gnu.org
2015-07-14 12:53 ` rguenth at gcc dot gnu.org
2015-07-14 13:02 ` doko at gcc dot gnu.org
2015-07-16  9:15 ` rguenth at gcc dot gnu.org
2015-07-21 22:10 ` wschmidt at gcc dot gnu.org
2015-07-22 13:54 ` wschmidt at gcc dot gnu.org [this message]
2015-07-22 13:55 ` wschmidt at gcc dot gnu.org
2015-07-22 14:07 ` wschmidt at gcc dot gnu.org
2015-07-22 14:28 ` wschmidt at gcc dot gnu.org
2015-07-24 19:58 ` doko at gcc dot gnu.org
2015-07-27 17:05 ` doko 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-66868-4-8dumlOSJ3j@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).