public inbox for gcc-regression@sourceware.org
help / color / mirror / Atom feed
From: "H. J. Lu" <hjl@sc.intel.com>
To: skpgkp2@gmail.com, hjl.tools@gmail.com, gcc-regression@gcc.gnu.org
Subject: Regressions on native/master at commit r12-6148 vs commit r12-6146 on Linux/x86_64
Date: Wed, 29 Dec 2021 18:41:19 -0800 [thread overview]
Message-ID: <20211230024119.1F1103E001F@gnu-clx-1.sc.intel.com> (raw)
New failures:
FAIL: gcc.misc-tests/godump-1.c scan-file (?n)^type _tsbf_gaps struct { bf1 uint8; c uint8; bf2 uint8; Godump_0_pad \\[2\\]byte; s uint16; Godump_1_align \\[0\\]int32; }$
FAIL: gcc.misc-tests/godump-1.c scan-file (?n)^type _tsbf_pad16_1 struct { Godump_0_pad \\[1\\]byte; c uint8; Godump_1_align \\[0\\]int16; }$
FAIL: gcc.misc-tests/godump-1.c scan-file (?n)^type _tsbf_pad16_2 struct { Godump_0_pad \\[2\\]byte; c uint8; Godump_1_pad \\[.\\]byte; Godump_2_align \\[0\\]int16; }$
FAIL: gcc.misc-tests/godump-1.c scan-file (?n)^type _tsbf_pad32_1 struct { Godump_0_pad \\[1\\]byte; c uint8; Godump_1_pad \\[.\\]byte; Godump_2_align \\[0\\]int32; }$
FAIL: gcc.misc-tests/godump-1.c scan-file (?n)^type _tsbf_pad32_2 struct { Godump_0_pad \\[4\\]byte; c uint8; Godump_1_pad \\[.\\]byte; Godump_2_align \\[0\\]int32; }$
FAIL: gcc.misc-tests/godump-1.c scan-file (?n)^type _tsbf_pad64_1 struct { Godump_0_pad \\[1\\]byte; c uint8; Godump_1_pad \\[.\\]byte; Godump_2_align \\[0\\]int64; }$
FAIL: gcc.misc-tests/godump-1.c scan-file (?n)^type _tsbf_pad64_2 struct { Godump_0_pad \\[8\\]byte; c uint8; Godump_1_pad \\[.\\]byte; Godump_2_align \\[0\\]int64; }$
FAIL: gcc.misc-tests/godump-1.c scan-file (?n)^type _tsn_anon struct { a uint8; s uint16; b uint8; Godump_0_pad \\[.\\]byte; Godump_1_align \\[0\\]int16; }$
FAIL: gcc.misc-tests/godump-1.c scan-file (?n)^type _ts_nested2 struct { u struct { Godump_0_pad \\[4\\]byte; Godump_1_pad \\[2\\]byte; s int16; c int8; Godump_2_pad \\[1\\]byte; Godump_3_pad \\[2\\]byte; Godump_4_align \\[0\\]u?int32; }; }$
FAIL: gcc.misc-tests/godump-1.c scan-file (?n)^type _ts_nested struct { u struct { s int16; Godump_0_pad \\[2\\]byte; Godump_1_align \\[0\\]u?int32; }; }$
FAIL: gcc.misc-tests/godump-1.c scan-file (?n)^type _tsu_anon struct { c uint8; Godump_0_pad \\[7\\]byte; Godump_1_align \\[0\\]u?int64; }$
FAIL: gcc.misc-tests/godump-1.c scan-file (?n)^type _tu1 struct { c uint8; Godump_0_pad \\[.\\]byte; Godump_1_align \\[0\\]u?int64; }$
FAIL: gcc.misc-tests/godump-1.c scan-file (?n)^type _tu3_size struct { ca \\[4\\+1\\]uint8; Godump_0_pad \\[.\\]byte; Godump_1_align \\[0\\]u?int64; }$
FAIL: gcc.misc-tests/godump-1.c scan-file (?n)^type _tu_nested2 struct { u struct { Godump_0_pad \\[4\\]byte; Godump_1_pad \\[2\\]byte; s int16; c int8; Godump_2_pad \\[1\\]byte; Godump_3_pad \\[2\\]byte; Godump_4_align \\[0\\]u?int32; }; }$
FAIL: gcc.misc-tests/godump-1.c scan-file (?n)^type _tu_nested struct { u struct { s int16; Godump_0_pad \\[2\\]byte; Godump_1_align \\[0\\]u?int32; }; }$
FAIL: gcc.misc-tests/godump-1.c scan-file (?n)^type _tu_size struct { ca \\[4\\+1\\]uint8; Godump_0_pad \\[.\\]byte; Godump_1_align \\[0\\]u?int64; }$
FAIL: gcc.misc-tests/godump-1.c scan-file (?n)^var _sbf_gaps struct { bf1 uint8; c uint8; bf2 uint8; Godump_0_pad \\[2\\]byte; s uint16; Godump_1_align \\[0\\]int32; }$
FAIL: gcc.misc-tests/godump-1.c scan-file (?n)^var _sbf_pad16_1 struct { Godump_0_pad \\[1\\]byte; c uint8; Godump_1_align \\[0\\]int16; }$
FAIL: gcc.misc-tests/godump-1.c scan-file (?n)^var _sbf_pad16_2 struct { Godump_0_pad \\[2\\]byte; c uint8; Godump_1_pad \\[.\\]byte; Godump_2_align \\[0\\]int16; }$
FAIL: gcc.misc-tests/godump-1.c scan-file (?n)^var _sbf_pad32_1 struct { Godump_0_pad \\[1\\]byte; c uint8; Godump_1_pad \\[.\\]byte; Godump_2_align \\[0\\]int32; }$
FAIL: gcc.misc-tests/godump-1.c scan-file (?n)^var _sbf_pad32_2 struct { Godump_0_pad \\[4\\]byte; c uint8; Godump_1_pad \\[.\\]byte; Godump_2_align \\[0\\]int32; }$
FAIL: gcc.misc-tests/godump-1.c scan-file (?n)^var _sbf_pad64_1 struct { Godump_0_pad \\[1\\]byte; c uint8; Godump_1_pad \\[.\\]byte; Godump_2_align \\[0\\]int64; }$
FAIL: gcc.misc-tests/godump-1.c scan-file (?n)^var _sbf_pad64_2 struct { Godump_0_pad \\[8\\]byte; c uint8; Godump_1_pad \\[.\\]byte; Godump_2_align \\[0\\]int64; }$
FAIL: gcc.misc-tests/godump-1.c scan-file (?n)^var _sn_anon struct { a uint8; s uint16; b uint8; Godump_0_pad \\[.\\]byte; Godump_1_align \\[0\\]int16; }$
FAIL: gcc.misc-tests/godump-1.c scan-file (?n)^var _s_nested2 struct { u struct { Godump_0_pad \\[4\\]byte; Godump_1_pad \\[2\\]byte; s int16; c int8; Godump_2_pad \\[1\\]byte; Godump_3_pad \\[2\\]byte; Godump_4_align \\[0\\]u?int32; }; }$
FAIL: gcc.misc-tests/godump-1.c scan-file (?n)^var _s_nested struct { u struct { s int16; Godump_0_pad \\[2\\]byte; Godump_1_align \\[0\\]u?int32; }; }$
FAIL: gcc.misc-tests/godump-1.c scan-file (?n)^var _su_anon struct { c uint8; Godump_0_pad \\[7\\]byte; Godump_1_align \\[0\\]u?int64; }$
FAIL: gcc.misc-tests/godump-1.c scan-file (?n)^var _u1 struct { c uint8; Godump_0_pad \\[.\\]byte; Godump_1_align \\[0\\]u?int64; }$
FAIL: gcc.misc-tests/godump-1.c scan-file (?n)^var _u3_size struct { ca \\[4\\+1\\]uint8; Godump_0_pad \\[.\\]byte; Godump_1_align \\[0\\]u?int64; }$
FAIL: gcc.misc-tests/godump-1.c scan-file (?n)^var _u_nested2 struct { u struct { Godump_0_pad \\[4\\]byte; Godump_1_pad \\[2\\]byte; s int16; c int8; Godump_2_pad \\[1\\]byte; Godump_3_pad \\[2\\]byte; Godump_4_align \\[0\\]u?int32; }; }$
FAIL: gcc.misc-tests/godump-1.c scan-file (?n)^var _u_nested struct { u struct { s int16; Godump_0_pad \\[2\\]byte; Godump_1_align \\[0\\]u?int32; }; }$
FAIL: gcc.misc-tests/godump-1.c scan-file (?n)^var _u_size struct { ca \\[4\\+1\\]uint8; Godump_0_pad \\[.\\]byte; Godump_1_align \\[0\\]u?int64; }$
New passes:
reply other threads:[~2021-12-30 2:41 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=20211230024119.1F1103E001F@gnu-clx-1.sc.intel.com \
--to=hjl@sc.intel.com \
--cc=gcc-regression@gcc.gnu.org \
--cc=hjl.tools@gmail.com \
--cc=skpgkp2@gmail.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).