public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Bernhard Fischer <rep.dot.nop@gmail.com>
To: Tobias Burnus <burnus@net-b.de>
Cc: FX Coudert <fxcoudert@gmail.com>,
	Thomas Koenig <tkoenig@alice-dsl.net>,
		fortran@gcc.gnu.org, gcc-patches@gcc.gnu.org
Subject: Re: [patch, libfortran] PR 32858 - printf()-capabilities for 	runtime_error
Date: Mon, 30 Jul 2007 09:42:00 -0000	[thread overview]
Message-ID: <20070730091425.GB23273@aon.at> (raw)
In-Reply-To: <46ADA47A.7070900@net-b.de>

On Mon, Jul 30, 2007 at 10:42:34AM +0200, Tobias Burnus wrote:
>FX Coudert wrote:
>> I daresay I'm a bit more anxious than Jerry about the portability of
>> the system you're introducing, and the functions you're using. Are we
>> garanteed that sprintf is available on all platforms?
>I don't know but it is used by:
>libcpp/macro.c, libcpp/charset.c,
>libgcc/config/libbid/bid128_to_string.c, libiberty/strerror.c,
>libobjc/archive.c.
>
>Still, it cannot harm to check MinGW ...

It's part of ISO C and SUSv3 (
http://www.opengroup.org/onlinepubs/009695399/functions/sprintf.html )

and since other parts of GCC already use it it should be safe (for
platforms that do not adhere to ISO C nor SUS the other parts of GCC
would already come with a replacement func, i assume).

cheers,

      reply	other threads:[~2007-07-30  9:14 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-29 19:15 Thomas Koenig
2007-07-29 20:02 ` Thomas Koenig
2007-07-29 20:08   ` Thomas Koenig
2007-07-29 20:08 ` Jerry DeLisle
2007-07-29 20:37 ` FX Coudert
2007-07-30  8:58   ` Tobias Burnus
2007-07-30  9:42     ` Bernhard Fischer [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=20070730091425.GB23273@aon.at \
    --to=rep.dot.nop@gmail.com \
    --cc=burnus@net-b.de \
    --cc=fortran@gcc.gnu.org \
    --cc=fxcoudert@gmail.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=tkoenig@alice-dsl.net \
    /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).