From: "Joseph S. Myers" <joseph@codesourcery.com>
To: Kai Tietz <Kai.Tietz@onevision.com>
Cc: Danny Smith <dansmister@gmail.com>,
GCC Patches <gcc-patches@gcc.gnu.org>,
NightStrike <nightstrike@gmail.com>
Subject: Re: Ping - old patch from April - mingw support for I32/I64 MS printf formatters to c-format.c
Date: Mon, 07 Jan 2008 14:44:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.64.0801071229580.24818@digraph.polyomino.org.uk> (raw)
In-Reply-To: <OFD8E09BCD.E7899FFC-ONC12573C9.0037DD89-C12573C9.003A2D35@onevision.de>
On Mon, 7 Jan 2008, Kai Tietz wrote:
> Ok, while running the testsuite I noticed, that at some places the
> formatter "%ld" is used together with an "int" type, which isn't marked to
> produce a warning. Which is at least for x86_64 linux targets a problem. I
> see on my tests that it got warned correctly as it should be a long.
> Just for "printf/scanf/strftime" formatters, there are some problems, the
> other formatters seems to work as before.
If you are referring to the tests asserting that C99 functions do not have
default attributes in -std=c89 mode, then indeed those will need
separating from some of the other tests when you make most of the tests be
of functions using gnu_printf etc. attributes when run got MinGW targets.
If you are referring to something else, you need to cite specific lines of
specific files and specific diagnostics or lack thereof to explain what
you are referring to.
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2008-01-07 12:33 UTC|newest]
Thread overview: 61+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-04 17:55 NightStrike
2007-12-04 18:32 ` Joseph S. Myers
2007-12-05 21:35 ` NightStrike
2007-12-05 22:53 ` Joseph S. Myers
2007-12-18 14:06 ` Kai Tietz
2007-12-18 16:30 ` Joseph S. Myers
2007-12-18 21:14 ` Danny Smith
2007-12-20 13:00 ` Kai Tietz
2007-12-20 14:16 ` Joseph S. Myers
2007-12-20 14:30 ` Kai Tietz
2007-12-21 14:03 ` Kai Tietz
2007-12-21 14:38 ` Joseph S. Myers
2008-01-07 13:56 ` Kai Tietz
2008-01-07 14:44 ` Joseph S. Myers [this message]
2008-01-07 16:26 ` Kai Tietz
2008-01-08 14:37 ` Kai Tietz
2008-01-08 18:18 ` Joseph S. Myers
2008-01-15 16:45 ` Kai Tietz
2008-01-16 16:14 Kai Tietz
[not found] <Pine.LNX.4.64.0801312346090.5937@digraph.polyomino.org.uk>
2008-02-01 11:04 ` Kai Tietz
2008-02-01 15:52 ` Joseph S. Myers
2008-02-04 14:23 ` Kai Tietz
2008-02-13 18:32 ` Joseph S. Myers
2008-02-19 9:22 ` Kai Tietz
2008-02-19 12:38 ` Joseph S. Myers
2008-02-19 13:30 ` Kai Tietz
2008-02-19 14:10 ` Joseph S. Myers
2008-02-19 15:16 ` Kai Tietz
2008-02-25 16:46 ` NightStrike
2008-02-25 16:58 ` Joseph S. Myers
2008-02-25 17:42 ` NightStrike
2008-02-25 18:53 ` Joseph S. Myers
2008-03-04 19:25 ` Joseph S. Myers
2008-03-10 11:06 ` Kai Tietz
2008-03-10 22:29 ` Joseph S. Myers
2008-03-13 0:03 ` Danny Smith
2008-03-13 8:43 ` Kai Tietz
2008-03-13 9:29 ` Kai Tietz
2008-03-13 19:24 ` Ralf Wildenhues
2008-03-14 9:32 ` Kai Tietz
2008-03-13 20:52 ` Danny Smith
2008-03-14 11:00 ` Kai Tietz
2008-03-16 5:54 ` Danny Smith
2008-03-16 12:16 ` Kai Tietz
2008-03-18 13:20 ` Kai Tietz
2008-03-18 13:44 ` NightStrike
2008-03-18 13:51 ` Kai Tietz
2008-03-18 15:07 ` Kai Tietz
2008-03-19 5:01 ` NightStrike
2008-03-19 6:22 ` Danny Smith
2008-03-19 9:42 ` Kai Tietz
2008-03-19 13:43 ` NightStrike
2008-03-19 13:51 ` NightStrike
2008-03-20 1:18 ` Danny Smith
2008-03-20 1:18 ` NightStrike
2008-03-20 9:54 ` Kai Tietz
2008-02-13 21:27 ` Danny Smith
2008-02-19 9:17 ` Kai Tietz
2008-03-13 22:38 FX Coudert
2008-03-14 1:33 ` Joseph S. Myers
2008-03-16 7:58 ` Danny Smith
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=Pine.LNX.4.64.0801071229580.24818@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=Kai.Tietz@onevision.com \
--cc=dansmister@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=nightstrike@gmail.com \
/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).