public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jgreenhalgh at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/68134] [6 Regression] float64x1_t comparison ICE on aarch64-none-elf Date: Wed, 28 Oct 2015 14:43:00 -0000 [thread overview] Message-ID: <bug-68134-4-l4oEQZ5be8@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-68134-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68134 --- Comment #2 from James Greenhalgh <jgreenhalgh at gcc dot gnu.org> --- Created attachment 36608 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=36608&action=edit testcasem, no arm_neon.h dependency Second testcase stripping the arm_neon.h stuff and using only GCC vector extensions. I couldn't get this to fail on s390 or i386 (two other targets which V1DF mode stuff in their back-end).
prev parent reply other threads:[~2015-10-28 14:43 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-10-28 12:20 [Bug middle-end/68134] New: vector-of-one-int64_t " jgreenhalgh at gcc dot gnu.org 2015-10-28 12:24 ` [Bug middle-end/68134] [6 Regression] " ktkachov at gcc dot gnu.org 2015-10-28 12:26 ` rguenth at gcc dot gnu.org 2015-10-28 14:43 ` jgreenhalgh at gcc dot gnu.org [this message]
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-68134-4-l4oEQZ5be8@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: linkBe 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).