public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "uecker at eecs dot berkeley.edu" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/97702] comma operator does not drop qualifiers during lvalue conversion Date: Thu, 26 Nov 2020 07:27:11 +0000 [thread overview] Message-ID: <bug-97702-4-Puo9h8qgOB@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-97702-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97702 --- Comment #6 from Martin Uecker <uecker at eecs dot berkeley.edu> --- https://gcc.gnu.org/git/gitweb.cgi?p=gcc.git;h=32934a4f45a72144cdcd0712cc294fe88c36f13d Author Martin Uecker <muecker@gwdg.de> Fri, 20 Nov 2020 06:21:40 +0000 (07:21 +0100) commit 32934a4f45a72144cdcd0712cc294fe88c36f13d C: Drop qualifiers during lvalue conversion [PR97702] 2020-11-20 Martin Uecker <muecker@gwdg.de> gcc/ * gimplify.c (gimplify_modify_expr_rhs): Optimizie NOP_EXPRs that contain compound literals. gcc/c/ * c-typeck.c (convert_lvalue_to_rvalue): Drop qualifiers. gcc/testsuite/ * gcc.dg/cond-constqual-1.c: Adapt test. * gcc.dg/lvalue-11.c: New test. * gcc.dg/pr60195.c: Add warning.
next prev parent reply other threads:[~2020-11-26 7:27 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-11-03 14:48 [Bug c/97702] New: " uecker at eecs dot berkeley.edu 2020-11-03 18:16 ` [Bug c/97702] " joseph at codesourcery dot com 2020-11-03 21:05 ` uecker at eecs dot berkeley.edu 2020-11-03 22:02 ` joseph at codesourcery dot com 2020-11-05 9:55 ` redi at gcc dot gnu.org 2020-11-05 17:27 ` joseph at codesourcery dot com 2020-11-26 7:27 ` uecker at eecs dot berkeley.edu [this message] 2020-12-23 12:34 ` muecker at gwdg dot de
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-97702-4-Puo9h8qgOB@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).