public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/51360] [4.6 Regression] spurious unused-but-set-variable warning for var used in OpenMP pragma Date: Thu, 09 Feb 2012 17:16:00 -0000 [thread overview] Message-ID: <bug-51360-4-3xwws4IMzm@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-51360-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51360 --- Comment #5 from Jakub Jelinek <jakub at gcc dot gnu.org> 2012-02-09 17:15:39 UTC --- Author: jakub Date: Thu Feb 9 17:15:29 2012 New Revision: 184049 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=184049 Log: Backported from mainline 2011-12-15 Jakub Jelinek <jakub@redhat.com> PR c/51360 * c-parser.c (c_parser_omp_clause_num_threads, c_parser_omp_clause_schedule): Call mark_exp_read. * semantics.c (finish_omp_clauses): For OMP_CLAUSE_NUM_THREADS_EXPR and OMP_CLAUSE_SCHEDULE_CHUNK_EXPR call mark_rvalue_use. * gcc.dg/gomp/pr51360.c: New test. * g++.dg/gomp/pr51360.C: New test. * g++.dg/gomp/pr51360-2.C: New test. Added: branches/gcc-4_6-branch/gcc/testsuite/g++.dg/gomp/pr51360-2.C branches/gcc-4_6-branch/gcc/testsuite/g++.dg/gomp/pr51360.C branches/gcc-4_6-branch/gcc/testsuite/gcc.dg/gomp/pr51360.c Modified: branches/gcc-4_6-branch/gcc/ChangeLog branches/gcc-4_6-branch/gcc/c-parser.c branches/gcc-4_6-branch/gcc/cp/ChangeLog branches/gcc-4_6-branch/gcc/cp/semantics.c branches/gcc-4_6-branch/gcc/testsuite/ChangeLog
next prev parent reply other threads:[~2012-02-09 17:16 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-11-30 17:20 [Bug c/51360] New: " kmccarty at gmail dot com 2011-12-14 23:51 ` [Bug c/51360] [4.6/4.7 Regression] " pinskia at gcc dot gnu.org 2011-12-15 13:38 ` jakub at gcc dot gnu.org 2011-12-15 17:51 ` jakub at gcc dot gnu.org 2011-12-15 20:51 ` [Bug c/51360] [4.6 " jakub at gcc dot gnu.org 2012-02-09 17:16 ` jakub at gcc dot gnu.org [this message] 2012-02-09 17:41 ` jakub 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-51360-4-3xwws4IMzm@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).