public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: nick <xerofoify@gmail.com>
To: gcc-patches@gcc.gnu.org
Subject: Patch that fix PR80188
Date: Fri, 29 Sep 2017 17:31:00 -0000	[thread overview]
Message-ID: <dc2298d5-eb2f-f890-3375-39fc6386e371@gmail.com> (raw)

Greetings,

I don't have write access so can someone commit this bug fix as it fixes,
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80188. 

Author: Nicholas Krause <xerofoify@gmail.com>
Date:   Fri Sep 29 11:39:46 2017 -0400

    This patch fixes, https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80188
    which reports that the char* pointer reason is not being translated
    properly when the error message from the function,
    maybe_complain_about_tail_call arises. Fix it by wrapping it in the
    N_ macro to translate to the proper language of the user. No new
    test cases are required due to the triviality of the bug.

diff --git a/gcc/calls.c b/gcc/calls.c
index 6bd025ed197..cfdd6b2cf6b 100644
--- a/gcc/calls.c
+++ b/gcc/calls.c
@@ -1516,7 +1516,7 @@ maybe_complain_about_tail_call (tree call_expr, const char *reason)
   if (!CALL_EXPR_MUST_TAIL_CALL (call_expr))
     return;
 
-  error_at (EXPR_LOCATION (call_expr), "cannot tail-call: %s", reason);
+  error_at (EXPR_LOCATION (call_expr), "cannot tail-call: %s", N_(reason));
 }
 
 /* Fill in ARGS_SIZE and ARGS array based on the parameters found in

Thanks,

Nick 

             reply	other threads:[~2017-09-29 17:31 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-29 17:31 nick [this message]
2017-09-29 17:48 Bernd Edlinger
2017-09-29 18:22 ` nick
2017-09-29 19:50   ` Bernd Edlinger

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=dc2298d5-eb2f-f890-3375-39fc6386e371@gmail.com \
    --to=xerofoify@gmail.com \
    --cc=gcc-patches@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).