This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Patch: PR preprocessor/19753


This patch fixes PR preprocessor/19753.

The report is that a setting like LANG=de_DE does not interact
gracefully with ccache, because GCC translates the strings
"<built-in>" and "<command-line>", which end up in the .i file.

This patch removes the translation.

I realize that translating these strings is probably done for error
reporting purposes.  I don't find this very compelling (but then I'm
not in the target audience for this translation) so I thought I would
submit the obvious patch to see what other folks think.

I suppose another approach would be to add a special case for these
file names elsewhere in the compiler -- i.e., leave them untranslated
in the .i file but then translate them if showing them to the user.

Bootstrapped and regression tested on x86 FC6.

Ok?

Tom

:ADDPATCH preprocessor:

2006-12-29  Tom Tromey  <tromey@redhat.com>

	PR preprocessor/19753:
	* c-opts.c (finish_options): Don't localize "<built-in>" or
	"<command-line>".

Index: gcc/c-opts.c
===================================================================
--- gcc/c-opts.c	(revision 120096)
+++ gcc/c-opts.c	(working copy)
@@ -1392,7 +1392,7 @@
 
       cb_file_change (parse_in,
 		      linemap_add (&line_table, LC_RENAME, 0,
-				   _("<built-in>"), 0));
+				   "<built-in>", 0));
 
       cpp_init_builtins (parse_in, flag_hosted);
       c_cpp_builtins (parse_in);
@@ -1410,7 +1410,7 @@
 
       cb_file_change (parse_in,
 		      linemap_add (&line_table, LC_RENAME, 0,
-				   _("<command-line>"), 0));
+				   "<command-line>", 0));
 
       for (i = 0; i < deferred_count; i++)
 	{


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]