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/67730] [5/6 Regression] No warning when returning NULL in void function
Date: Fri, 02 Oct 2015 18:02:00 -0000	[thread overview]
Message-ID: <bug-67730-4-JhvIsB3gTc@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-67730-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67730

--- Comment #7 from Marek Polacek <mpolacek at gcc dot gnu.org> ---
Author: mpolacek
Date: Fri Oct  2 18:01:50 2015
New Revision: 228408

URL: https://gcc.gnu.org/viewcvs?rev=228408&root=gcc&view=rev
Log:
        PR c/67730
        * c-typeck.c (convert_for_assignment): Use the expansion point
        location throughout.

        * gcc.dg/pr67730-1.c: New test.
        * gcc.dg/pr67730-2.c: New test.
        * gcc.dg/pr67730.h: New test.

Added:
    trunk/gcc/testsuite/gcc.dg/pr67730-1.c
    trunk/gcc/testsuite/gcc.dg/pr67730-2.c
    trunk/gcc/testsuite/gcc.dg/pr67730.h
Modified:
    trunk/gcc/c/ChangeLog
    trunk/gcc/c/c-typeck.c
    trunk/gcc/testsuite/ChangeLog


  parent reply	other threads:[~2015-10-02 18:02 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-27 11:19 [Bug c/67730] New: [5.2 " damwdan at gmail dot com
2015-09-28 11:04 ` [Bug c/67730] [5/6 " rguenth at gcc dot gnu.org
2015-09-28 17:07 ` joseph at codesourcery dot com
2015-09-28 18:14 ` manu at gcc dot gnu.org
2015-09-28 18:29 ` manu at gcc dot gnu.org
2015-09-29 14:24 ` mpolacek at gcc dot gnu.org
2015-09-30 11:27 ` mpolacek at gcc dot gnu.org
2015-09-30 12:21 ` mpolacek at gcc dot gnu.org
2015-10-02 18:02 ` mpolacek at gcc dot gnu.org [this message]
2015-10-05 12:35 ` [Bug c/67730] [5 " mpolacek at gcc dot gnu.org
2015-10-05 12:37 ` 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-67730-4-JhvIsB3gTc@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).