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 01:03:38 +0000	[thread overview]
Message-ID: <bug-94449-4-UsZVAWmZlN@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

Kewen Lin <linkw at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |ASSIGNED

--- Comment #8 from Kewen Lin <linkw at gcc dot gnu.org> ---
May I ask for the configuration option? 

I used x86_64 machine in CFarm with cpuinfo

processor       : 0
vendor_id       : GenuineIntel
cpu family      : 6
model           : 45
model name      : Intel(R) Xeon(R) CPU E5-2660 0 @ 2.20GHz
...

I was unable to reproduce it with default configuration setting, but I was able
to 
see the ICE with -march=znver2 specified for the failures. 
I suspected there was some basic arch setting in your configuration? If so, I'm
wondering one more reasonable configuration option for E5 machine, it would
help to catch regression failures like this. Thanks in advance!

  parent reply	other threads:[~2020-04-02  1:03 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 [this message]
2020-04-02  1:06 ` hjl.tools at gmail dot com
2020-04-02  2:28 ` linkw at gcc dot gnu.org
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-UsZVAWmZlN@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).