public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "dmalcolm at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug lto/65378] Tweak to wording of -Wodr message Date: Tue, 10 Mar 2015 15:45:00 -0000 [thread overview] Message-ID: <bug-65378-4-MKBQ0MAl9M@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-65378-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65378 --- Comment #1 from David Malcolm <dmalcolm at gcc dot gnu.org> --- (In reply to David Malcolm from comment #0) [...] > Message in question is here in ipa-devirt.c: > if (!warning_at (DECL_SOURCE_LOCATION (TYPE_NAME (t1)), OPT_Wodr, > "type %qT violates one definition rule", > t1)) and in 5 other places in that file. >From gcc-bugs-return-479992-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Mar 10 15:58:27 2015 Return-Path: <gcc-bugs-return-479992-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org> Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 98329 invoked by alias); 10 Mar 2015 15:58:27 -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 89840 invoked by uid 55); 10 Mar 2015 15:58:19 -0000 From: "mpolacek at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug sanitizer/65367] [5 Regression] indefinite loop occurs with sanitize enabled and certain optimization options Date: Tue, 10 Mar 2015 15:58: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: X-Bugzilla-Severity: normal X-Bugzilla-Who: mpolacek at gcc dot gnu.org X-Bugzilla-Status: ASSIGNED X-Bugzilla-Priority: P1 X-Bugzilla-Assigned-To: mpolacek at gcc dot gnu.org X-Bugzilla-Target-Milestone: 5.0 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: <bug-65367-4-7JAKLFMYfr@http.gcc.gnu.org/bugzilla/> In-Reply-To: <bug-65367-4@http.gcc.gnu.org/bugzilla/> References: <bug-65367-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-03/txt/msg01136.txt.bz2 Content-length: 642 https://gcc.gnu.org/bugzilla/show_bug.cgi?ide367 --- Comment #4 from Marek Polacek <mpolacek at gcc dot gnu.org> --- Author: mpolacek Date: Tue Mar 10 15:57:45 2015 New Revision: 221325 URL: https://gcc.gnu.org/viewcvs?rev"1325&root=gcc&view=rev Log: PR sanitizer/65367 * ubsan.c (ubsan_expand_objsize_ifn): Update GSI instead of GSI_ORIG when only removing the statement. Handle expanding UBSAN_OBJECT_SIZE separately. * c-c++-common/ubsan/pr65367.c: New test. Added: trunk/gcc/testsuite/c-c++-common/ubsan/pr65367.c Modified: trunk/gcc/ChangeLog trunk/gcc/testsuite/ChangeLog trunk/gcc/ubsan.c
next prev parent reply other threads:[~2015-03-10 15:45 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-03-10 15:42 [Bug lto/65378] New: " dmalcolm at gcc dot gnu.org 2015-03-10 15:45 ` dmalcolm at gcc dot gnu.org [this message] 2015-04-27 7:52 ` [Bug lto/65378] " hubicka at gcc dot gnu.org 2015-06-08 20:38 ` hubicka 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-65378-4-MKBQ0MAl9M@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).