public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "kargl at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/36161] gfc_error formats are not marked gcc-internal-format in po file
Date: Mon, 19 May 2008 19:48:00 -0000	[thread overview]
Message-ID: <20080519194809.11419.qmail@sourceware.org> (raw)
In-Reply-To: <bug-36161-10888@http.gcc.gnu.org/bugzilla/>



------- Comment #1 from kargl at gcc dot gnu dot org  2008-05-19 19:48 -------
I don't understand this PR.  gfc_error's format strings may look
like C's printf format strings, but these are different.  These
format strings are parsed and used by gfortran, and are not passed
directly to libc.  So, gfc_error (and gfc_warning) format strings
should be marked no-c-format.


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=36161


  reply	other threads:[~2008-05-19 19:48 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-06 19:41 [Bug fortran/36161] New: " goeran at uddeborg dot se
2008-05-19 19:48 ` kargl at gcc dot gnu dot org [this message]
2008-05-19 20:16 ` [Bug fortran/36161] " goeran at uddeborg dot se
2009-01-03 23:58 ` dfranke at gcc dot gnu dot org
2009-03-28 16:39 ` fxcoudert at gcc dot gnu dot org
2009-03-28 18:27 ` goeran at uddeborg dot se
2009-03-29 16:53 ` goeran at uddeborg dot se
2009-03-29 16:55 ` bruno at clisp dot org
2009-03-29 17:00 ` joseph at codesourcery dot com
2009-12-07 18:40 ` dfranke at gcc dot gnu dot org
2009-12-17 20:54 ` pault at gcc dot gnu dot org
2009-12-17 23:07 ` dfranke at gcc dot gnu dot org
2009-12-18  9:56 ` burnus at gcc dot gnu dot org
2009-12-18 18:27 ` dfranke at gcc dot gnu dot org
2009-12-19 11:39 ` dfranke at gcc dot gnu dot org
2010-01-04  7:46 ` burnus at gcc dot gnu dot org
2010-01-04 21:01 ` burnus at gcc dot gnu dot org
2010-01-04 21:13 ` burnus at gcc dot gnu dot org
2010-01-11 17:27 ` goeran at uddeborg dot se
2010-01-11 20:21 ` burnus at gcc dot gnu dot org
2010-01-11 21:02 ` goeran at uddeborg dot se

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=20080519194809.11419.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: 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).