public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "hp at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug testsuite/60173] [4.9 Regression]: gcc.dg/binop-xor1.c scan-tree-dump-times
Date: Sat, 22 Feb 2014 16:58:00 -0000	[thread overview]
Message-ID: <bug-60173-4-fnNxvsxjrL@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-60173-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #2 from Hans-Peter Nilsson <hp at gcc dot gnu.org> ---
Author: hp
Date: Sat Feb 22 16:58:06 2014
New Revision: 208044

URL: http://gcc.gnu.org/viewcvs?rev=208044&root=gcc&view=rev
Log:
    PR testsuite/60173
    * lib/target-supports.exp
    (check_effective_target_logical_op_short_circuit): Add cris-*-*
    and crisv32-*-* to list.

Modified:
    trunk/gcc/testsuite/ChangeLog
    trunk/gcc/testsuite/lib/target-supports.exp


  parent reply	other threads:[~2014-02-22 16:58 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-13 10:14 [Bug regression/60173] New: " hp at gcc dot gnu.org
2014-02-22 16:48 ` [Bug testsuite/60173] " hp at gcc dot gnu.org
2014-02-22 16:58 ` hp at gcc dot gnu.org [this message]
2014-02-22 17:02 ` hp 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-60173-4-fnNxvsxjrL@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).