public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "amker.cheng at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/60363] [4.9 Regression]: logical_op_short_circuit, gcc.dg/tree-ssa/ssa-dom-thread-4.c scan-tree-dump-times dom1 "Threaded" 4
Date: Mon, 31 Mar 2014 09:39:00 -0000	[thread overview]
Message-ID: <bug-60363-4-rKUSfEJhIm@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-60363-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #10 from bin.cheng <amker.cheng at gmail dot com> ---
Patch sent at http://gcc.gnu.org/ml/gcc-patches/2014-03/msg00857.html , but it
need to wait for stage 1.

I will xfail it for now.


  parent reply	other threads:[~2014-03-31  9:39 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-28  1:31 [Bug regression/60363] New: " hp at gcc dot gnu.org
2014-02-28  1:32 ` [Bug regression/60363] " hp at gcc dot gnu.org
2014-02-28  9:18 ` rguenth at gcc dot gnu.org
2014-03-09 13:31 ` amker.cheng at gmail dot com
2014-03-09 13:36 ` amker.cheng at gmail dot com
2014-03-09 15:00 ` amker.cheng at gmail dot com
2014-03-11  9:16 ` amker.cheng at gmail dot com
2014-03-11 11:34 ` amker.cheng at gmail dot com
2014-03-12 10:27 ` amker.cheng at gmail dot com
2014-03-31  9:29 ` [Bug tree-optimization/60363] " rguenth at gcc dot gnu.org
2014-03-31  9:39 ` amker.cheng at gmail dot com [this message]
2014-03-31 13:26 ` law at redhat dot com
2014-04-01 12:41 ` rguenth at gcc dot gnu.org
2014-04-22 11:35 ` [Bug tree-optimization/60363] [4.9/4.10 " jakub at gcc dot gnu.org
2014-05-06  7:16 ` amker.cheng at gmail dot com
2014-05-06  8:25 ` rguenth 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-60363-4-rKUSfEJhIm@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).