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 rust/29859] Printing rust expressions with simple arithmetic gets wrong result Date: Mon, 12 Dec 2022 13:44:30 +0000 [thread overview] Message-ID: <bug-29859-4717-awjI0KgvX4@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-29859-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=29859 --- Comment #6 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Tom Tromey <tromey@sourceware.org>: https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=67a8c89601f6e1947484d5de23411634fef92e68 commit 67a8c89601f6e1947484d5de23411634fef92e68 Author: Tom Tromey <tom@tromey.com> Date: Mon Dec 12 06:36:55 2022 -0700 Another Rust operator precedence bug My earlier patch to fix PR rust/29859 introduced a new operator precedence bug in the Rust parser. Assignment operators are right-associative in Rust. And, while this doesn't often matter, as Rust assignments always have the value (), still as a matter of principle we should get this correct. Bug: https://sourceware.org/bugzilla/show_bug.cgi?id=29859 -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2022-12-12 13:44 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-12-06 12:33 [Bug rust/29859] New: " bpeeluk at yahoo dot co.uk 2022-12-06 14:14 ` [Bug rust/29859] " tromey at sourceware dot org 2022-12-06 14:43 ` cvs-commit at gcc dot gnu.org 2022-12-06 14:43 ` tromey at sourceware dot org 2022-12-06 15:37 ` bpeeluk at yahoo dot co.uk 2022-12-06 22:14 ` tromey at sourceware dot org 2022-12-12 13:44 ` cvs-commit at gcc dot gnu.org [this message] 2022-12-12 13:46 ` tromey at sourceware dot org 2022-12-13 13:01 ` bpeeluk at yahoo dot co.uk
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-29859-4717-awjI0KgvX4@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).