public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "u17263 at att dot net" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/64868] New: C front-end rejects valid syntax.
Date: Thu, 29 Jan 2015 20:38:00 -0000 [thread overview]
Message-ID: <bug-64868-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64868
Bug ID: 64868
Summary: C front-end rejects valid syntax.
Product: gcc
Version: 5.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c
Assignee: unassigned at gcc dot gnu.org
Reporter: u17263 at att dot net
Created attachment 34620
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=34620&action=edit
test case
gcc version: 5.0.0 / svn: r220249
gcc -Wall -fopenmp -c bug-9.c
bug-9.c: In function ‘foo’:
bug-9.c:12:22: error: invalid form of ‘#pragma omp atomic’ before ‘;’ token
fgot = 1.0 / fgot;
>From gcc-bugs-return-475451-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 29 20:40:47 2015
Return-Path: <gcc-bugs-return-475451-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 29196 invoked by alias); 29 Jan 2015 20:40:47 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 29133 invoked by uid 55); 29 Jan 2015 20:40:42 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug sanitizer/64717] -fsanitize=vptr leads to warning:=?UTF-8?Q? ‘?=<anonymous>=?UTF-8?Q?’ may be used uninitialized in this function ?=[-Wmaybe-uninitialized]
Date: Thu, 29 Jan 2015 20:40:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: sanitizer
X-Bugzilla-Version: 5.0
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-64717-4-ZgeCbmpeKD@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-64717-4@http.gcc.gnu.org/bugzilla/>
References: <bug-64717-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2015-01/txt/msg03445.txt.bz2
Content-length: 640
https://gcc.gnu.org/bugzilla/show_bug.cgi?idd717
--- Comment #4 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Author: jakub
Date: Thu Jan 29 20:40:07 2015
New Revision: 220262
URL: https://gcc.gnu.org/viewcvs?rev"0262&root=gcc&view=rev
Log:
PR c++/64717
* cp-ubsan.c (cp_ubsan_instrument_vptr): Don't wrap vptr
into SAVE_EXPR.
* g++.dg/ubsan/pr64717-1.C: New test.
* g++.dg/ubsan/pr64717-2.C: New test.
Added:
trunk/gcc/testsuite/g++.dg/ubsan/pr64717-1.C
trunk/gcc/testsuite/g++.dg/ubsan/pr64717-2.C
Modified:
trunk/gcc/cp/ChangeLog
trunk/gcc/cp/cp-ubsan.c
trunk/gcc/testsuite/ChangeLog
next reply other threads:[~2015-01-29 20:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-29 20:38 u17263 at att dot net [this message]
2015-02-04 19:12 ` [Bug c/64868] " jakub at gcc dot gnu.org
2015-02-04 22:33 ` jakub at gcc dot gnu.org
2015-02-04 22:39 ` jakub at gcc dot gnu.org
2015-02-11 14:44 ` jakub at gcc dot gnu.org
2015-10-08 16:03 ` tschwinge 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-64868-4@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: link
Be 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).