* Alan Ong ([EMAIL PROTECTED]) [20061201 03:35]:
> Hello,
>I am trying to compile my code with hard-coded Japanese Kanji and
> full-width katakana string text but the compiler view some of the text
> as escape characters.
Please ask on [EMAIL PROTECTED] This list deals with the development of
On Sun, 4 Dec 2005 20:07:33 -0500 (EST), Jack Howarth wrote:
>swigpy.cc: In function 'int SWIGPY_Python_ConvertPtr(PyObject*, void**,
>swig_typ
>e_info*, int)':
>swigpy.cc:620: warning: dereferencing type-punned pointer will break
>strict-alia
>sing rules
My recent encounters with python (in m
* Christophe Jaillet ([EMAIL PROTECTED]) [20060109 20:00]:
> in file 'bt-load.c', in function 'augment_live_range', some memory is
> xmalloc'ed. It seems to be possible to never free it, if all the first tests
> are true.
This is now PR 25739.
Philipp
* Ian Lance Taylor (i...@google.com) [20100413 00:41]:
> Details of GIMPLE IR: poor.
> Details of tree IR: poor.
> How to write a new optimization pass: poor.
> How to write a new frontend: nonexistent.
> General overview of compiler source: nonexistent.
> Overview of internal compiler datastructu
On Sun, 28 Dec 2008 14:24:22 -0500, you wrote:
>I have SLES9 and Linux-2.6.5-7.97 kernel install on i586 intel 32 bit
>machine. The compiler is gcc-c++3.3.3-43.24. I want to upgrade to
>GCC4.3.2. My question are: Would this upgrade work with
>SLES9?
This is the wrong list for such questions
On Fri, 23 Apr 2010 16:23:29 +0200, Manuel López-Ibáñez
wrote:
>Great! Go ahead, please. The wiki is easy to edit.
Finally I got around to do it.
Editing is easy ... kind of :) Creating the Links was easy but I
failed do discover how I could actually make them point to other wiki
pages.
> Bon
On Sun, 15 Jan 2006 10:40:19 -0600, Perry Smith wrote:
> From Andreas's reply, it may not. In AIX, they want the message to
>come out in the user's native language so they print out the
>translated message (that comes from a separate file).
It's the same with gettext. You have a file contain
On Fri, 11 Jan 2008 09:59:41 -0800, Brian D. McGrew wrote:
>We're trying to move to 64-Bit now and this same code that has compiled
> for years is barking about operators cannot be overloaded.
Please stick to gcc-help, as gcc is the wrong list for such questions.
Philipp
* Simon Toth ([EMAIL PROTECTED]) [20080718 13:16]:
> Is there any full database of gcc warnings and errors?
AFAIK, there isn't one. I guess your best choice is gcc.pot (i.e. the
message catalog) in the po subdir.
Philipp
