public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/106459] Compiler crashing for loongarch64-linux-gnu on windows Date: Thu, 25 Aug 2022 01:19:53 +0000 [thread overview] Message-ID: <bug-106459-4-aN9EFkRO0w@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-106459-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106459 --- Comment #7 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Chenghua Xu <paulhua@gcc.gnu.org>: https://gcc.gnu.org/g:b169b67d7dafe2b786f87c31d6b2efc603fd880c commit r13-2195-gb169b67d7dafe2b786f87c31d6b2efc603fd880c Author: Chenghua Xu <xuchenghua@loongson.cn> Date: Wed Aug 24 15:34:07 2022 +0800 LoongArch: Fix pr106459 by use HWIT instead of 1UL. gcc/ChangeLog: PR target/106459 * config/loongarch/loongarch.cc (loongarch_build_integer): Use HOST_WIDE_INT. * config/loongarch/loongarch.h (IMM_REACH): Likewise. (HWIT_1U): New Defined. (LU12I_OPERAND): Use HOST_WIDE_INT. (LU32I_OPERAND): Likewise. (LU52I_OPERAND): Likewise. (HWIT_UC_0xFFF): Likwise. gcc/testsuite/ChangeLog: * gcc.target/loongarch/pr106459.c: New test.
next prev parent reply other threads:[~2022-08-25 1:19 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-07-27 23:12 [Bug other/106459] New: " unlvsur at live dot com 2022-07-27 23:15 ` [Bug other/106459] " unlvsur at live dot com 2022-07-27 23:17 ` [Bug c++/106459] " unlvsur at live dot com 2022-07-27 23:23 ` [Bug target/106459] " pinskia at gcc dot gnu.org 2022-07-27 23:40 ` pinskia at gcc dot gnu.org 2022-07-27 23:42 ` pinskia at gcc dot gnu.org 2022-08-24 7:50 ` paul.hua.gm at gmail dot com 2022-08-25 1:19 ` cvs-commit at gcc dot gnu.org [this message] 2022-08-25 1:42 ` cvs-commit at gcc dot gnu.org 2023-01-08 7:48 ` pinskia 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-106459-4-aN9EFkRO0w@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: linkBe 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).