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++/40202] warning about passing non-POD objects through �...� should include name and location of declaration being called
Date: Thu, 29 Sep 2011 21:08:00 -0000 [thread overview]
Message-ID: <bug-40202-4-NeeHlRaCf4@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-40202-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=40202
--- Comment #8 from Manuel López-Ibáñez <manu at gcc dot gnu.org> 2011-09-29 20:54:46 UTC ---
(In reply to comment #4)
> Manuel, do you have an opinion about this rather old issue? In the meanwhile,
> the warning became an hard error, when it applies. Thus the original testcase
> is just accepted, and this variant:
Paolo, thanks for asking my opinion! As a user, I would appreciate an extra
inform saying where the variadic function is declared, like g++ does for other
diagnostics. But since I don't know how hard is to get that location at the
error point, and I am not volunteering to do the work...
BTW, I think it is great that you are triaging and fixing so many C++
diagnostic bugs, it was sorely needed.
next prev parent reply other threads:[~2011-09-29 20:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-40202-4@http.gcc.gnu.org/bugzilla/>
2011-09-29 16:25 ` paolo.carlini at oracle dot com
2011-09-29 16:27 ` redi at gcc dot gnu.org
2011-09-29 17:32 ` paolo.carlini at oracle dot com
2011-09-29 17:35 ` redi at gcc dot gnu.org
2011-09-29 21:08 ` manu at gcc dot gnu.org [this message]
2011-09-29 22:20 ` paolo.carlini at oracle dot com
2009-05-19 20:32 [Bug c++/40202] New: warning about passing non-POD objects through ... " jason dot orendorff at gmail dot com
2009-05-19 22:04 ` [Bug c++/40202] " pinskia at gcc dot gnu dot 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-40202-4-NeeHlRaCf4@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).