public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "linkw at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/94449] [10 Regression] FAIL: gcc.c-torture/execute/pr92904.c gcc.dg/torture/pr48731.c
Date: Thu, 02 Apr 2020 02:28:57 +0000 [thread overview]
Message-ID: <bug-94449-4-zbAiD3DOGR@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-94449-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94449
--- Comment #10 from Kewen Lin <linkw at gcc dot gnu.org> ---
(In reply to H.J. Lu from comment #9)
> (In reply to Kewen Lin from comment #8)
> > May I ask for the configuration option?
> >
> > I used x86_64 machine in CFarm with cpuinfo
> >
>
> I used
>
> --prefix=/usr/10.0.1 --enable-clocale=gnu --with-system-zlib --enable-shared
> --enable-cet --with-demangler-in-ld --with-fpmath=sse
Thanks, but it didn't work on my side. I guessed it's due to different native.
gcc -march=native -Q --help=target|grep march
-march= corei7-avx
$ ./t.sh -march=znver2
internal compiler error: verify_ssa failed
$ ./t.sh -march=icelake-server
internal compiler error: verify_ssa failed
$ ./t.sh -march=corei7-avx ==> works fine.
I guess I can't just specify the arch option like --with-arch=znver2 for
configure, since native arch probably misses the support of some instructions
for znver2? I have no idea on x86 arch, is it possible?
next prev parent reply other threads:[~2020-04-02 2:28 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-01 17:14 [Bug middle-end/94449] New: " hjl.tools at gmail dot com
2020-04-01 22:26 ` [Bug middle-end/94449] " hjl.tools at gmail dot com
2020-04-01 22:29 ` hjl.tools at gmail dot com
2020-04-01 22:38 ` hjl.tools at gmail dot com
2020-04-01 22:48 ` hjl.tools at gmail dot com
2020-04-01 22:50 ` hjl.tools at gmail dot com
2020-04-01 22:52 ` hjl.tools at gmail dot com
2020-04-02 0:01 ` linkw at gcc dot gnu.org
2020-04-02 1:03 ` linkw at gcc dot gnu.org
2020-04-02 1:06 ` hjl.tools at gmail dot com
2020-04-02 2:28 ` linkw at gcc dot gnu.org [this message]
2020-04-02 2:38 ` linkw at gcc dot gnu.org
2020-04-02 6:28 ` linkw 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-94449-4-zbAiD3DOGR@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).