public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Marc Glisse <marc.glisse@inria.fr>
To: Andreas Schwab <schwab@linux-m68k.org>
Cc: Richard Sandiford <rdsandiford@googlemail.com>, gcc-patches@gcc.gnu.org
Subject: Re: Warn when returning the address of a temporary (middle-end) v2
Date: Sun, 27 Jul 2014 21:05:00 -0000	[thread overview]
Message-ID: <alpine.DEB.2.11.1407272229380.7232@laptop-mg.saclay.inria.fr> (raw)
In-Reply-To: <87ha22twlf.fsf@igel.home>

On Sun, 27 Jul 2014, Andreas Schwab wrote:

> Marc Glisse <marc.glisse@inria.fr> writes:
>
>> On Sun, 27 Jul 2014, Richard Sandiford wrote:
>>
>>> Marc Glisse <marc.glisse@inria.fr> writes:
>>>> +		      if (always_executed)
>>>> +			msg = "function returns address of local variable";
>>>> +		      else
>>>> +			msg = "function may return address of local variable";
>>>
>>> I think you need _(...) here, unless some magic makes that unnecessary now.
>>
>> I just tried to see how the magic happens when someone calls error_at, and
>> it goes through diagnostic_set_info, which contains:
>>
>> diagnostic_set_info_translated (diagnostic, _(gmsgid), args, location, kind);
>>
>> So I think the _(...) is already taken care of. But I don't know that code
>> at all and I could easily have looked at it wrong.
>
> If the msgid is not a direct argument of the diagnostic function you
> need to mark the string with N_(...).

Ah, ok, thanks.
Actually, shouldn't it be G_ instead? That's what ABOUT-GCC-NLS seems to 
suggest since 2005, though I don't expect it makes any difference for 
simple strings.

-- 
Marc Glisse

  reply	other threads:[~2014-07-27 20:50 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-22 18:20 Marc Glisse
2014-06-29  9:22 ` Marc Glisse
2014-06-30 21:04   ` Jeff Law
2014-06-30 21:37     ` Marc Glisse
2014-07-02 12:19       ` Alan Modra
2014-07-02 12:41         ` Marc Glisse
2014-07-02 22:39         ` Jeff Law
2014-07-02 22:46       ` Jeff Law
2014-07-18  5:06 ` Jeff Law
2014-07-22  9:04   ` Marc Glisse
2014-07-31  4:54     ` Jeff Law
2014-07-27 18:20 ` Richard Sandiford
2014-07-27 19:09   ` Marc Glisse
2014-07-27 20:45     ` Andreas Schwab
2014-07-27 21:05       ` Marc Glisse [this message]
2014-07-29 19:00   ` Marc Glisse
2014-07-29 19:13     ` David Malcolm
2014-07-29 19:22       ` Marek Polacek
2014-07-29 19:47         ` David Malcolm
2014-07-29 19:28       ` Marc Glisse
2014-07-30 12:00       ` Marc Glisse
2014-07-31  4:58         ` Jeff Law

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=alpine.DEB.2.11.1407272229380.7232@laptop-mg.saclay.inria.fr \
    --to=marc.glisse@inria.fr \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=rdsandiford@googlemail.com \
    --cc=schwab@linux-m68k.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).