From: "Li, Pan2" <pan2.li@intel.com>
To: "Maciej W. Rozycki" <macro@orcam.me.uk>
Cc: Richard Biener <richard.guenther@gmail.com>,
"gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>,
"juzhe.zhong@rivai.ai" <juzhe.zhong@rivai.ai>,
"kito.cheng@gmail.com" <kito.cheng@gmail.com>,
"tamar.christina@arm.com" <tamar.christina@arm.com>
Subject: RE: [PATCH v7] Match: Support more form for scalar unsigned SAT_ADD
Date: Thu, 13 Jun 2024 13:00:09 +0000 [thread overview]
Message-ID: <MW5PR11MB5908B65152D25C042C12C936A9C12@MW5PR11MB5908.namprd11.prod.outlook.com> (raw)
In-Reply-To: <alpine.DEB.2.21.2406131204110.9248@angie.orcam.me.uk>
Could you please help to update the upstream for another try ?
Should be fixed by this commit https://github.com/gcc-mirror/gcc/commit/d03ff3fd3e2da1352a404e3c53fe61314569345c.
Feel free to ping me if any questions or concerns.
Pan
-----Original Message-----
From: Maciej W. Rozycki <macro@orcam.me.uk>
Sent: Thursday, June 13, 2024 8:01 PM
To: Li, Pan2 <pan2.li@intel.com>
Cc: Richard Biener <richard.guenther@gmail.com>; gcc-patches@gcc.gnu.org; juzhe.zhong@rivai.ai; kito.cheng@gmail.com; tamar.christina@arm.com
Subject: RE: [PATCH v7] Match: Support more form for scalar unsigned SAT_ADD
On Thu, 6 Jun 2024, Li, Pan2 wrote:
> Committed, thanks Richard.
This has broken glibc building for the `riscv64-linux-gnu' target:
iovsprintf.c: In function '__vsprintf_internal':
iovsprintf.c:34:1: error: definition in block 5 follows the use
34 | __vsprintf_internal (char *string, size_t maxlen,
| ^~~~~~~~~~~~~~~~~~~
for SSA_NAME: _9 in statement:
prephitmp_36 = (char *) _9;
during GIMPLE pass: widening_mul
iovsprintf.c:34:1: internal compiler error: verify_ssa failed
0x7fffb1474bf7 generic_start_main
../csu/libc-start.c:308
0x7fffb1474de3 __libc_start_main
../sysdeps/unix/sysv/linux/powerpc/libc-start.c:116
Please submit a full bug report, with preprocessed source (by using -freport-bug).
Please include the complete backtrace with any bug report.
See <https://gcc.gnu.org/bugs/> for instructions.
Use just `riscv64-linux-gnu -O2' on the attached preprocessed source to
reproduce. This builds just fine up to e14afbe2d1c6^ and then breaks with
the message quoted.
Shall I investigate it further or will you be able to figure it out with
the information supplied what's wrong?
Maciej
next prev parent reply other threads:[~2024-06-13 13:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-06 13:37 pan2.li
2024-06-06 14:04 ` Richard Biener
2024-06-06 22:59 ` Li, Pan2
2024-06-13 12:00 ` Maciej W. Rozycki
2024-06-13 13:00 ` Li, Pan2 [this message]
2024-06-13 16:14 ` Maciej W. Rozycki
2024-06-14 1:21 ` Li, Pan2
2024-06-14 6:04 ` Richard Biener
2024-06-14 22:27 ` Maciej W. Rozycki
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=MW5PR11MB5908B65152D25C042C12C936A9C12@MW5PR11MB5908.namprd11.prod.outlook.com \
--to=pan2.li@intel.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=juzhe.zhong@rivai.ai \
--cc=kito.cheng@gmail.com \
--cc=macro@orcam.me.uk \
--cc=richard.guenther@gmail.com \
--cc=tamar.christina@arm.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).