public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "manu at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/61018] [5 Regression] -Wvarargs does not print warning for member functions
Date: Mon, 10 Nov 2014 16:51:00 -0000	[thread overview]
Message-ID: <bug-61018-4-nofrlZNu5o@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-61018-4@http.gcc.gnu.org/bugzilla/>

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

Manuel López-Ibáñez <manu at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |manu at gcc dot gnu.org
   Target Milestone|---                         |5.0
            Summary|-Wvarargs does not print    |[5 Regression] -Wvarargs
                   |warning for member          |does not print warning for
                   |functions                   |member functions

--- Comment #1 from Manuel López-Ibáñez <manu at gcc dot gnu.org> ---
It seems a regression, because GCC 4.4.5 did warn.
>From gcc-bugs-return-466275-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Nov 10 16:55:43 2014
Return-Path: <gcc-bugs-return-466275-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 16218 invoked by alias); 10 Nov 2014 16:55:43 -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 16154 invoked by uid 48); 10 Nov 2014 16:55:39 -0000
From: "howarth at bromo dot med.uc.edu" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/61407] Build errors on latest OS X 10.10 Yosemite with Xcode 6 on GCC 4.8.3
Date: Mon, 10 Nov 2014 16:55:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: howarth at bromo dot med.uc.edu
X-Bugzilla-Status: NEW
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-61407-4-bnzl140H5N@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-61407-4@http.gcc.gnu.org/bugzilla/>
References: <bug-61407-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: 2014-11/txt/msg00747.txt.bz2
Content-length: 1301

https://gcc.gnu.org/bugzilla/show_bug.cgi?ida407

howarth at bromo dot med.uc.edu changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |howarth at bromo dot med.uc.edu

--- Comment #46 from howarth at bromo dot med.uc.edu ---
(In reply to Francois-Xavier Coudert from comment #45)
> (In reply to Jeremy Huddleston Sequoia from comment #42)
> > The committed patch is incorrect.  It makes an invalid assumption which
> > breaks the usage of deployment targets such as 10.9.3.
>
> All Apple doc I can find has deployment targets of the form 10.x or 10.x.0
> (where x is integer, but not only one digit).

If Jeremy really disagreed on that change, he hasn't acted on it in the gcc49
MacPorts packaging that he maintains (which still uses the original proposed
patch from https://gcc.gnu.org/ml/gcc-patches/2014-08/msg02428.html). FYI, as
far as llvm-gcc 4.2.1 is concerned, in my fink legacy package for Apple's
llvm-gcc 4.2.1, I used a back port of our patch,
http://fink.cvs.sourceforge.net/viewvc/fink/dists/10.7/stable/main/finkinfo/languages/llvm-gcc42-yosemite.patch.
Neither gcc 4.9.2 nor the patched llvm-gcc 4.2.1 has shown any problems on OS X
10.9.5.


  parent reply	other threads:[~2014-11-10 16:51 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-30 16:33 [Bug c++/61018] New: -Wvarargs does not print warning for memer functions bilbotheelffriend at gmail dot com
2014-11-10 13:41 ` [Bug c++/61018] -Wvarargs does not print warning for member functions redi at gcc dot gnu.org
2014-11-10 16:51 ` manu at gcc dot gnu.org [this message]
2014-12-01 12:01 ` [Bug c++/61018] [4.8/4.9/5 Regression] " rguenth at gcc dot gnu.org
2014-12-09 17:38 ` [Bug middle-end/61018] " jason at gcc dot gnu.org
2014-12-19 13:43 ` jakub at gcc dot gnu.org
2015-02-24 11:31 ` 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-61018-4-nofrlZNu5o@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).