public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "mpolacek at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/60195] Strange warnings using atomic types Date: Wed, 19 Feb 2014 06:30:00 -0000 [thread overview] Message-ID: <bug-60195-4-A6mTkIuGL7@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-60195-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60195 --- Comment #2 from Marek Polacek <mpolacek at gcc dot gnu.org> --- Author: mpolacek Date: Wed Feb 19 06:29:49 2014 New Revision: 207873 URL: http://gcc.gnu.org/viewcvs?rev=207873&root=gcc&view=rev Log: PR c/60195 c/ * c-typeck.c (convert_lvalue_to_rvalue): Set TREE_NO_WARNING on tmp. Call mark_exp_read on exp.value. (build_atomic_assign): Set TREE_NO_WARNING on val and old. Set TREE_ADDRESSABLE on old instead of val. (emit_side_effect_warnings): Warn only if RHS has !TREE_NO_WARNING. testsuite/ * gcc.dg/pr60195.c: New test. Added: trunk/gcc/testsuite/gcc.dg/pr60195.c Modified: trunk/gcc/c/ChangeLog trunk/gcc/c/c-typeck.c trunk/gcc/testsuite/ChangeLog
next prev parent reply other threads:[~2014-02-19 6:30 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-02-14 14:17 [Bug c/60195] New: " jp.deplaix at gmail dot com 2014-02-17 20:42 ` [Bug c/60195] " mpolacek at gcc dot gnu.org 2014-02-19 6:30 ` mpolacek at gcc dot gnu.org [this message] 2014-02-19 6:31 ` mpolacek 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-60195-4-A6mTkIuGL7@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).