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++/19447] unknown conversion type character `q' in format Date: Sat, 15 Jan 2005 04:38:00 -0000 [thread overview] Message-ID: <20050115043855.9448.qmail@sourceware.org> (raw) In-Reply-To: <20050114181419.19447.corsepiu@gcc.gnu.org> ------- Additional Comments From pinskia at gcc dot gnu dot org 2005-01-15 04:38 ------- No what I am saying if you want accurate warnings for building 4.0.0, you need 4.0.0 but since we don't build cross compilers with -Werror for a reason. Basically we added more formating in 4.0.0 which are not supported at all in 3.4.0 so warning about them in 3.4.0 is useful as you know that you messed up when back porting a patch to the 3.4.0 when compiling natively. If you use an earlier version of gcc than 3.4.0, you don't get this warnings at all. The only way to fix this would depend on using the formatting warnings only for that certain version of gcc (I would assume that the formatting warnings are useful even if we don't support them in 3.4.0 because you can reconize what version you using to cross compile with). And yes you should be really using the same version to cross compile with as then it does not get confussing when something gets miscompiled (which has been known to happen in the past). -- What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution| |WONTFIX http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19447
prev parent reply other threads:[~2005-01-15 4:38 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2005-01-14 18:14 [Bug c++/19447] New: " corsepiu at gcc dot gnu dot org 2005-01-14 18:36 ` [Bug c++/19447] " pinskia at gcc dot gnu dot org 2005-01-15 4:32 ` corsepiu at gcc dot gnu dot org 2005-01-15 4:38 ` pinskia at gcc dot gnu dot org [this message]
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=20050115043855.9448.qmail@sourceware.org \ --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).