public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug sim/27483] aarch64: adds test failing when adding 0x80000000 & 0xffffffff Date: Thu, 08 Apr 2021 01:53:22 +0000 [thread overview] Message-ID: <bug-27483-4717-MpMJuWy84M@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-27483-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=27483 --- Comment #8 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Jim Wilson <wilson@sourceware.org>: https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=0592e80bcf1bbab2fbbb110ea395f9608e4f594c commit 0592e80bcf1bbab2fbbb110ea395f9608e4f594c Author: Jim Wilson <jimw@sifive.com> Date: Wed Apr 7 18:51:52 2021 -0700 Aarch64 sim fix for gcc-10 miscompilation. This fixes a problem that occurs when compiled by gcc-10, as the code is relying on undefined overflow behavior. This is fixed by replacing compares between 32-bit and 64-bit results with compares that just use the 64-bit results with a cast. PR sim/27483 * simulator.c (set_flags_for_add32): Compare uresult against itself. Compare sresult against itself. -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2021-04-08 1:53 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-02-28 6:35 [Bug sim/27483] New: " vapier at gentoo dot org 2021-03-01 4:48 ` [Bug sim/27483] " wilson at gcc dot gnu.org 2021-03-01 8:30 ` schwab@linux-m68k.org 2021-03-01 16:43 ` wilson at gcc dot gnu.org 2021-03-01 16:55 ` schwab@linux-m68k.org 2021-03-01 23:28 ` wilson at gcc dot gnu.org 2021-03-02 8:43 ` schwab@linux-m68k.org 2021-03-07 18:48 ` vapier at gentoo dot org 2021-04-08 1:53 ` cvs-commit at gcc dot gnu.org [this message] 2021-04-08 1:59 ` wilson 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-27483-4717-MpMJuWy84M@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=gdb-prs@sourceware.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).