public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dcb314 at hotmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/100369] crash after error in gcc.target/aarch64/simd/vgetq_lane_s64_indices_1.c
Date: Mon, 17 May 2021 16:34:22 +0000 [thread overview]
Message-ID: <bug-100369-4-mhXw1PWZvA@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-100369-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100369
--- Comment #2 from David Binderman <dcb314 at hotmail dot com> ---
(In reply to Christophe Lyon from comment #1)
> Can you share details on how you get this error? (GCC configure options,
> command-line used to compile the testcase)
configure is
CC="clang -Wall -Wextra" CXX="clang++ -Wall -Wextra" \
../trunk/configure --prefix=/home/pi/gcc/results.20210516 \
--disable-multilib \
--disable-werror \
--with-pkgversion=$HASH \
--enable-checking=yes \
--enable-languages=c,c++,fortran \
--with-cpu=cortex-a72 \
--with-fpu=neon-fp-armv8 \
--with-float=hard \
--build=arm-linux-gnueabihf \
--host=arm-linux-gnueabihf \
--target=arm-linux-gnueabihf
sed 's/-O2/-O3 -march=native/' < Makefile > Makefile.tmp
diff Makefile Makefile.tmp
mv Makefile.tmp Makefile
Host machine is a raspberry pi 3B+. It is entirely possible the configure
is not quite optimal, although it seems to work.
The command line I used is
$ /home/pi/gcc/results.20210516/bin/gcc -c
gcc.target/aarch64/simd/vgetq_lane_s64_indices_1.c
The bug still seems to occur in yesterday's compiler.
next prev parent reply other threads:[~2021-05-17 16:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-01 7:10 [Bug target/100369] New: " dcb314 at hotmail dot com
2021-05-17 16:21 ` [Bug target/100369] " clyon at gcc dot gnu.org
2021-05-17 16:34 ` dcb314 at hotmail dot com [this message]
2021-05-18 9:08 ` acoplan at gcc dot gnu.org
2021-05-18 9:13 ` acoplan 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-100369-4-mhXw1PWZvA@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).