public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "michael.collison at linaro dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/63365] New: [ARM] Incorrect copy propagation for vclz intrinsic
Date: Thu, 25 Sep 2014 05:51:00 -0000	[thread overview]
Message-ID: <bug-63365-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 63365
           Summary: [ARM] Incorrect copy propagation for vclz intrinsic
           Product: gcc
           Version: 4.9.2
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: rtl-optimization
          Assignee: unassigned at gcc dot gnu.org
          Reporter: michael.collison at linaro dot org

Created attachment 33558
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=33558&action=edit
Test case demonstrating incorrect code generation for vclz

Compiling and executing the attached testcase at -O2 produces incorrect code
and execution results. Instead of code being generated for the vclz instruction
the compiler propagates an incorrect constant value for what it believes will
be the result of the instruction. The attached test case is part of a proposed
set of DejaGnu tests for neon intrinsics.

------------------------------------------------------------------------------
Target: arm-linux-gnueabihf

Configured with:
'/home/michael-collison/neon-intrinsic-build/snapshots/gcc.git~neon-intrinsic-christophe/configure'
--with-bugurl=https://bugs.launchpad.net/gcc-linaro
--with-mpc=/home/michael-collison/neon-intrinsic-build/builds/destdir/x86_64-unknown-linux-gnu
--with-mpfr=/home/michael-collison/neon-intrinsic-build/builds/destdir/x86_64-unknown-linux-gnu
--with-gmp=/home/michael-collison/neon-intrinsic-build/builds/destdir/x86_64-unknown-linux-gnu
--with-gnu-as --with-gnu-ld --disable-libstdcxx-pch --disable-libmudflap
--with-cloog=no --with-ppl=no --with-isl=no --disable-nls --enable-multiarch
--disable-multilib --enable-c99 --with-arch=armv7-a --with-fpu=vfpv3-d16
--with-float=hard --with-mode=thumb
--with-sysroot=/opt/linaro/sysroot-linaro_eglibc-2_19-arm-clean-linux-gnueabihf
--with-build-sysroot=/home/michael-collison/neon-intrinsic-build/sysroots/arm-clean-linux-gnueabihf
--enable-lto --enable-linker-build-id --enable-long-long
--enable-languages=c,c++,fortran,go,lto
--with-bugurl=https://bugs.launchpad.net/gcc-linaro --with-pkgversion='Linaro
GCC 2014.08' --build=x86_64-unknown-linux-gnu --host=x86_64-unknown-linux-gnu
--target=arm-clean-linux-gnueabihf
--prefix=/home/michael-collison/neon-intrinsic-build/builds/destdir/x86_64-unknown-linux-gnu

Thread model: posix

gcc version 4.10.0 20140812 (experimental) (Linaro GCC 2014.08)


             reply	other threads:[~2014-09-25  5:51 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-25  5:51 michael.collison at linaro dot org [this message]
2014-11-13 17:13 ` [Bug rtl-optimization/63365] " ramana 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-63365-4@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).