public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Paolo Carlini <paolo.carlini@oracle.com>
To: "gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Cc: Jason Merrill <jason@redhat.com>
Subject: [translation patch] Bunch of trivial PRs: 48638, 49517, 49704
Date: Wed, 19 Oct 2011 14:18:00 -0000	[thread overview]
Message-ID: <4E9ECC88.3050104@oracle.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 251 bytes --]

Hi,

a bunch of trivial fixes from Roland. The only one I deem *slightly* 
more controversial is "AST" uppercase instead of "ast" in 
cp/semantics.c, I'm gonna wait a bit in case Jason has a different 
opinion...

Thanks,
Paolo.

////////////////////

[-- Attachment #2: CL_48638_49517_49704 --]
[-- Type: text/plain, Size: 443 bytes --]

2011-10-19  Roland Stigge  <stigge@antcom.de>  

	PR translation/48638
	* plugin.c (add_new_plugin): Fix typo in fatal_error message.

2011-10-19  Roland Stigge  <stigge@antcom.de>  

	PR translation/49517
	* config/rx/rx.c (rx_print_operand): Fix typo in warning message.

/cp
2011-10-19  Roland Stigge  <stigge@antcom.de>

	PR translation/49704    
	* semantics.c (potential_constant_expression_1): Use AST instead of
	ast in sorry message.

[-- Attachment #3: patch_48638_49517_49704 --]
[-- Type: text/plain, Size: 1714 bytes --]

Index: cp/semantics.c
===================================================================
--- cp/semantics.c	(revision 180185)
+++ cp/semantics.c	(working copy)
@@ -8341,7 +8341,7 @@ potential_constant_expression_1 (tree t, bool want
       return false;
 
     default:
-      sorry ("unexpected ast of kind %s", tree_code_name[TREE_CODE (t)]);
+      sorry ("unexpected AST of kind %s", tree_code_name[TREE_CODE (t)]);
       gcc_unreachable();
       return false;
     }
Index: plugin.c
===================================================================
--- plugin.c	(revision 180181)
+++ plugin.c	(working copy)
@@ -1,5 +1,5 @@
 /* Support for GCC plugin mechanism.
-   Copyright (C) 2009, 2010 Free Software Foundation, Inc.
+   Copyright (C) 2009, 2010, 2011 Free Software Foundation, Inc.
 
 This file is part of GCC.
 
@@ -149,7 +149,7 @@ add_new_plugin (const char* plugin_name)
 			    plugin_name, ".so", NULL);
       if (access (plugin_name, R_OK))
 	fatal_error
-	  ("inacessible plugin file %s expanded from short plugin name %s: %m",
+	  ("inaccessible plugin file %s expanded from short plugin name %s: %m",
 	   plugin_name, base_name);
     }
   else
Index: config/rx/rx.c
===================================================================
--- config/rx/rx.c	(revision 180181)
+++ config/rx/rx.c	(working copy)
@@ -637,7 +637,7 @@ rx_print_operand (FILE * file, rtx op, int letter)
 	case 0xb: fprintf (file, "fintv"); break;
 	case 0xc: fprintf (file, "intb"); break;
 	default:
-	  warning (0, "unreocgnized control register number: %d - using 'psw'",
+	  warning (0, "unrecognized control register number: %d - using 'psw'",
 		   (int) INTVAL (op));
 	  fprintf (file, "psw");
 	  break;

             reply	other threads:[~2011-10-19 13:14 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-19 14:18 Paolo Carlini [this message]
2011-10-19 14:20 ` Jason Merrill
2011-10-19 16:49 ` H.J. Lu

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=4E9ECC88.3050104@oracle.com \
    --to=paolo.carlini@oracle.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=jason@redhat.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).