From: "Joseph S. Myers" <joseph@codesourcery.com>
To: Andi Kleen <andi@firstfloor.org>
Cc: Richard Guenther <richard.guenther@gmail.com>,
gcc-patches@gcc.gnu.org, Andi Kleen <ak@linux.intel.com>
Subject: Re: [PATCH 2/2] Improve reporting of section conflict errors
Date: Thu, 16 Dec 2010 16:56:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.64.1012161540060.16840@digraph.polyomino.org.uk> (raw)
In-Reply-To: <20101216140106.GB20612@basil.fritz.box>
On Thu, 16 Dec 2010, Andi Kleen wrote:
> +/* Print section flags F into BUF */
End comment with ". */".
> + { "code", SECTION_CODE, 0 },
[...]
> + if (f)
> + sprintf (buf, "rest %x", f);
Are these strings meant to be English language or literal programming
language text? If English, there should be appropriate arrangements for
translation.
> + char buf[1024];
> +
I agree a variable size buffer would be better - but the minimum is
runtime checks to avoid overflow in the case of long translations etc. (so
don't use sprintf etc. without knowing there is enough space left at
runtime).
It would be nice to eliminate direct use of sprintf from GCC - even if you
do know there is enough space, using snprintf is better discipline. (And
asprintf/vasprintf - in favour of xasprintf/xvasprintf - if someone could
just approve <http://gcc.gnu.org/ml/gcc-patches/2009-11/msg01448.html and
<http://gcc.gnu.org/ml/gcc-patches/2009-11/msg01449.html>.)
> + inform (DECL_SOURCE_LOCATION (decl),
> + "New section declaration differs in: %s",
> + section_flags_string (buf, flags));
Diagnostics start with lowercase letters.
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2010-12-16 15:46 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-16 13:25 [PATCH 1/2] Fix -fno-lto (PR lto/46905) Andi Kleen
2010-12-16 13:26 ` [PATCH 2/2] Improve reporting of section conflict errors Andi Kleen
2010-12-16 13:32 ` Richard Guenther
2010-12-16 15:39 ` Andi Kleen
2010-12-16 15:46 ` Richard Guenther
2010-12-16 15:53 ` Andi Kleen
2010-12-16 16:56 ` Joseph S. Myers [this message]
2010-12-16 17:24 ` Andi Kleen
2010-12-16 20:37 ` H.J. Lu
2010-12-16 14:01 ` Nathan Froyd
2010-12-16 13:29 ` [PATCH 1/2] Fix -fno-lto (PR lto/46905) Richard Guenther
2010-12-16 13:30 ` Andi Kleen
2010-12-16 13:45 ` Richard Guenther
2010-12-16 16:09 ` Jan Hubicka
2010-12-16 16:44 ` Joseph S. Myers
2010-12-16 18:14 ` Andi Kleen
2010-12-18 20:44 ` Richard Guenther
2010-12-20 5:05 ` Andi Kleen
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.1012161540060.16840@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=ak@linux.intel.com \
--cc=andi@firstfloor.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=richard.guenther@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).