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/104842] mips: signed overflow in LUI_OPERAND Date: Wed, 09 Mar 2022 03:21:32 +0000 [thread overview] Message-ID: <bug-104842-4-4IOqopYZld@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-104842-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104842 --- Comment #1 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Xi Ruoyao <xry111@gcc.gnu.org>: https://gcc.gnu.org/g:2ab70a4a5c2d5a9ffb923f13b1c3b938c60dd0f0 commit r12-7555-g2ab70a4a5c2d5a9ffb923f13b1c3b938c60dd0f0 Author: Xi Ruoyao <xry111@mengyan1223.wang> Date: Wed Mar 9 01:08:58 2022 +0800 mips: avoid signed overflow in LUI_OPERAND [PR104842] gcc/ PR target/104842 * config/mips/mips.h (LUI_OPERAND): Cast the input to an unsigned value before adding an offset.
next prev parent reply other threads:[~2022-03-09 3:21 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-03-08 16:54 [Bug target/104842] New: " xry111 at mengyan1223 dot wang 2022-03-09 3:21 ` cvs-commit at gcc dot gnu.org [this message] 2022-03-09 3:22 ` [Bug target/104842] " xry111 at mengyan1223 dot wang
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-104842-4-4IOqopYZld@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).