public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/37724] New: "initialization from incompatible pointer type" does not say which field is being initialized Date: Fri, 03 Oct 2008 05:27:00 -0000 [thread overview] Message-ID: <bug-37724-6528@http.gcc.gnu.org/bugzilla/> (raw) When I was upgrading the PS3 toolchain I found it would have been useful to figure out which field of a struct was being initialized with this warning turned on. Take: struct f { int *a; }; char b[10]; struct f g = {b}; --- CUT --- Currently we just get: t.c:7: warning: initialization from incompatible pointer type But with a large macro like what is in GCC sources, it is hard to figure out which field has the incompatible pointer type. Likewise for the diffs in signedness warning. -- Summary: "initialization from incompatible pointer type" does not say which field is being initialized Product: gcc Version: 4.4.0 Status: UNCONFIRMED Keywords: diagnostic Severity: normal Priority: P3 Component: c AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: pinskia at gcc dot gnu dot org http://gcc.gnu.org/bugzilla/show_bug.cgi?id=37724
next reply other threads:[~2008-10-03 5:27 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2008-10-03 5:27 pinskia at gcc dot gnu dot org [this message] 2008-10-03 5:40 ` [Bug c/37724] " pinskia at gcc dot gnu dot org 2008-10-03 12:52 ` rguenth at gcc dot gnu dot org 2008-10-03 17:35 ` pinskia at gmail dot com 2008-10-03 20:43 ` pinskia at gcc dot gnu dot org 2009-04-22 20:59 ` pinskia at gcc dot gnu dot org 2010-04-09 2:19 ` pinskia at gcc dot gnu dot org 2010-05-28 17:15 ` pinskia at gcc dot gnu dot org 2010-06-08 3:57 ` pzhao at gcc dot gnu dot org 2010-06-08 4:02 ` pzhao 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-37724-6528@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).