From: "Joseph S. Myers" <joseph@codesourcery.com>
To: Kai Tietz <Kai.Tietz@onevision.com>, ktietz70@googlemail.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, 25 Feb 2008 18:53:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.64.0802251832110.25844@digraph.polyomino.org.uk> (raw)
In-Reply-To: <OFDAA0EC24.AF38BEB6-ONC12573F4.0050F748-C12573F4.0051880D@onevision.de>
On Tue, 19 Feb 2008, Kai Tietz wrote:
> * gcc/c-format.h: Add structure target_ovr_attr to hold
> system specific formatter names.
No "gcc/" in ChangeLog entries. Also note the proper style
* file (part of file): Message.
so "c-format.h (target_ovr_attr): New structure." (for example).
The use of "formatter" still needs changing to "format" throughout the
patch.
> + if (attr_name == NULL || *attr_name == 0 || strncmp (attr_name, "gcc_", 4) == 0)
Please ensure source lines are under 80 columns wide.
> + for (i = 0; gnu_target_overrides_format_attributes[i].named_attr_src != NULL; ++i)
Likewise.
> + /* Name of the single-character length modifier. If prefixed by
> + a zero character, it discribes a multi character length
"describes".
> + modifier, lile I64, I32, etc. */
"like".
> +/* Contains a pointer to type target_ovr_attr defining the target specific
> + overrides of formatter attributs. See format.h for structure definition. */
"attributes", and I think you mean c-format.h.
> Index: gcc/gcc/config/i386/msformat-c.c
Note that this part of the patch will need reviewing by a MinGW
maintainer.
> The parameter @var{archetype} determines how the format string is
> -interpreted, and should be @code{printf}, @code{scanf}, @code{strftime}
> -or @code{strfmon}. (You can also use @code{__printf__},
> -@code{__scanf__}, @code{__strftime__} or @code{__strfmon__}.) The
> -parameter @var{string-index} specifies which argument is the format
> -string argument (starting from 1), while @var{first-to-check} is the
> -number of the first argument to check against the format string. For
> -functions where the arguments are not available to be checked (such as
> +interpreted, and should be @code{printf}, @code{scanf}, @code{strftime},
> +@code{gnu_printf}, @code{gnu_scanf}, @code{gnu_strftime} or
> +@code{strfmon}. (You can also use @code{__printf__},
> +@code{__scanf__}, @code{__strftime__} or @code{__strfmon__}.) On
> +mingw targets there is also @code{ms_printf}, @code{ms_scanf}, and
"MinGW". And I think it's actually "Microsoft Windows targets", since
these appear to be available on Cygwin as well, judging by the config.gcc
patch.
> +@code{ms_strftime} present. The none target specific formatters are
> +always the variant of the system. The parameter @var{string-index}
"@var{archtype} values such as @code{printf} refer to the formats accepted
by the system's C run-time library, while @code{gnu_} values always refer
to the formats accepted by the GNU C Library. On Microsoft Windows
targets, @code{ms_} values refer to the formats accepted by the
@file{msvcrt.dll} library."
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2008-02-25 18:49 UTC|newest]
Thread overview: 63+ messages / expand[flat|nested] mbox.gz Atom feed top
[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 [this message]
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 9:12 ` [patch]: pr33617 vector modes have to be passed via memory for x86_64-pc-mingw32 Kai Tietz
2008-03-18 9:54 ` Kai Tietz
2008-03-18 13:20 ` Ping - old patch from April - mingw support for I32/I64 MS printf formatters to c-format.c 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
-- strict thread matches above, loose matches on Subject: below --
2008-01-16 16:14 Kai Tietz
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
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
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.0802251832110.25844@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=Kai.Tietz@onevision.com \
--cc=dansmister@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=ktietz70@googlemail.com \
--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).