public inbox for gcc-regression@sourceware.org
help / color / mirror / Atom feed
From: haochenj@shgcc06.sh.intel.com
To: <gcc-regression@gcc.gnu.org>,<haochen.jiang@intel.com>
Subject: Regressions on native/releases/gcc-13 at commit r13-8648 vs commit r13-8646 on Linux/x86_64
Date: Fri, 26 Apr 2024 03:18:32 +0800 (CST)	[thread overview]
Message-ID: <20240425191832.34F7514A1E37@shgcc06.sh.intel.com> (raw)

Regressions on releases/gcc-13 at commit r13-8648 vs commit r13-8646 on Linux/x86_64
New failures:
FAIL: gcc.dg/torture/builtin-fp-int-inexact-c2x.c   -O2 -flto -fuse-linker-plugin -fno-fat-lto-objects  execution test
FAIL: libgomp.c/../libgomp.c-c++-common/for-12.c execution test
FAIL: libgomp.c/../libgomp.c-c++-common/for-14.c execution test
FAIL: libgomp.c/../libgomp.c-c++-common/for-9.c execution test

New passes:

                 reply	other threads:[~2024-04-25 19:18 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20240425191832.34F7514A1E37@shgcc06.sh.intel.com \
    --to=haochenj@shgcc06.sh.intel.com \
    --cc=gcc-regression@gcc.gnu.org \
    --cc=haochen.jiang@intel.com \
    /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).