public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "christophe.lyon at st dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/61153] [ARM] vbic vorn tests fail
Date: Tue, 28 Oct 2014 14:50:00 -0000	[thread overview]
Message-ID: <bug-61153-4-BuKlnaqNEI@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-61153-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #11 from christophe.lyon at st dot com ---
(In reply to Ramana Radhakrishnan from comment #10)
> (In reply to Bernd Edlinger from comment #9)
> > Hi, these tests are still failing.
> > what are we gonna do about it?
>  
> 
> I am happy for a patch to delete them.
> 
> 
> Ramana

What about modifying the tests to use -O2 instead of -O0?

At least, this would enable checking that the expected instruction is
generated.


  parent reply	other threads:[~2014-10-28 14:40 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-12 12:06 [Bug target/61153] New: " christophe.lyon at st dot com
2014-05-12 12:44 ` [Bug target/61153] " ktkachov at gcc dot gnu.org
2014-05-12 12:47 ` christophe.lyon at st dot com
2014-05-12 12:56 ` ktkachov at gcc dot gnu.org
2014-05-12 13:10 ` ramana at gcc dot gnu.org
2014-05-12 13:11 ` ramana at gcc dot gnu.org
2014-05-12 13:18 ` christophe.lyon at st dot com
2014-05-12 13:19 ` christophe.lyon at st dot com
2014-05-12 13:22 ` ramana.radhakrishnan at arm dot com
2014-10-02  7:27 ` bernd.edlinger at hotmail dot de
2014-10-28 14:35 ` ramana at gcc dot gnu.org
2014-10-28 14:50 ` christophe.lyon at st dot com [this message]
2014-10-28 15:09 ` ramana at gcc dot gnu.org
2014-11-19 13:52 ` christophe.lyon at st dot com

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-61153-4-BuKlnaqNEI@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).