similar to: Why flash in Firefox doesn't always show Chinese words?

I use FreeBSD. Windows Firefox shows Chinese fine. But some simple windows programs just show black boxes instead. Is there a documentation anywhere explaining how to make Chinese fonts work? Yuri

Forwarding the patch to commits so that it doesn't get lost. Yuri -------- Original Message -------- From: - Fri Jun 03 12:15:47 2011 X-Mozilla-Status: 0011 X-Mozilla-Status2: 10000000 Return-Path: <llvmdev-bounces at cs.uiuc.edu> X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on mail1.rawbw.com X-Spam-Level: X-Spam-Status: No, score=-0.2 required=7.0

Because OS X is not an ELF target, and support was only implemented in LLVM for making ELFs with debug info. I think the docs I wrote on this may suggest that the FSF gdb 7.0+ will work, but that's not the case. Sent from phne Reid On Jan 4, 2011 10:50 PM, "Yuri" <yuri at rawbw.com> wrote: With the same source code, gdb on Linux shows function names and on MacOS it

I've had a request from one of my users to add Mandarin support. A few quick googles gets me nothing, nor looking for "adding language support". Anyone have a pointer to info on adding whatever packages/group packages I need? Thanks in advance. mark

Yuri, on which host? 2011/8/17 Yuri <yuri at rawbw.com>: > In r134967 it still worked, and in r137742 it now doesn't. > I used such flags: --enable-assertions --enable-shared --enable-libffi > --enable-debug-runtime --enable-debug-symbols --disable-optimized > > Before build would create directory tools/llvm-shlib under the build > tree. Now it is missing. In my

On Apr 17, 2013, at 7:26 PM, Yuri <yuri at rawbw.com> wrote: > On 10/02/2012 13:01, Duncan Sands wrote: >> >> I think Chris is the right person to look at this, hopefully he will. > > Now 5 months passed. I updated the patch for this current revision. > Can anybody review this and check in please? > > http://llvm.org/bugs/show_bug.cgi?id=13163 >

-Wenum-compare is buggy / bogus. We should turn this warning off in our build scripts if possible. On Tue, Jun 26, 2012 at 5:15 PM, Yuri <yuri at rawbw.com> wrote: > I just switched gcc from 4.6.2 to 4.7.1 and see the massive amount of > warnings, see few examples below. > They mostly didn't exist with gcc-4.6.2. > > rev.159224 > > Yuri > > >

I've built clang+llvm in an object directory successfully, and I'm sure others have. I'd guess the problem is the symlink, so I'd give it a shot without it. Reid On Thu, Jun 10, 2010 at 7:43 AM, Diego Iastrubni <diegoiast at gmail.com> wrote: > can you tell what commands exactly did you use? > > What I usually do is: > > svn co llvm... > mkdir

----- Original Message ---- > From: Chris Lattner <clattner at apple.com> > To: Yuri <yuri at rawbw.com> > Cc: llvmdev at cs.uiuc.edu > Sent: Sun, February 20, 2011 3:26:35 AM > Subject: Re: [LLVMdev] Announcing: LLVM 2.9 Tentative Release Schedule > > > On Feb 19, 2011, at 8:05 PM, Yuri wrote: > > > On 02/19/2011 14:52, Yuri wrote: > >>

Have you found http://llvm.org/docs/DebuggingJITedCode.html? The JIT already has support for something like this for gdb's benefit. Perftools and valgrind just don't know how to find it yet. On Sat, Jun 19, 2010 at 2:03 PM, Yuri <yuri at rawbw.com> wrote: > This new option (--jit-emit-debug-function-range) will allow to output > function information for memory ranges that

can you tell what commands exactly did you use? What I usually do is: svn co llvm... mkdir llvm/tools/clang svn co llvm/tools/clang mkdir cmake-build cd cmake-build cmake ../ make Try something similar by running "../configure", it should work. On Thu, Jun 10, 2010 at 11:23 AM, Yuri <yuri at rawbw.com> wrote: > I did these steps: > * checked out llvm trunk, and clang

On Thu, Feb 20, 2014 at 1:58 PM, Yuri <yuri at rawbw.com> wrote: > On 02/18/2014 00:44, 杨勇勇 wrote: > >> I ported llvm backend and lldb recently. Both tools can basically work. >> lldb is able to debug programs in asm style and frame unwinding is OK. >> >> But "frame variable XX" does not work because lldb is not able to >> determine >> the

I just switched gcc from 4.6.2 to 4.7.1 and see the massive amount of warnings, see few examples below. They mostly didn't exist with gcc-4.6.2. rev.159224 Yuri /usr/home/yuri/llvm-2012-06/latest-unpatched/llvm-fix/include/llvm/ADT/PointerUnion.h:56:10: warning: enumeral mismatch in conditional expression:

Yuri <yuri at rawbw.com> writes: > How can I copy the value from another BB? > PHI instruction with one argument would fit, but it requires that all > arguments are in immediately preceding BBs. Using a value is not restricted to the BB where you created it.

hi ambika, I am not sure about this solution as i just started working in this field. How about taking analogy of a problem which ask us to find nearest common parent of two nodes in a tree. Let me know if I can be corrected. - Anubhav intern IIT M B. Tech 4th year CSE VIT University, Vellore. On 31 May 2010 22:30, <llvmdev-request at cs.uiuc.edu> wrote: > Send LLVMdev mailing list

Hello Yuri, Did you look at http://cfe.llvm.org/compatibility.html yet? --Sam ----- Original Message ----- > From: Yuri <yuri at rawbw.com> > To: LLVM Developers Mailing List <llvmdev at cs.uiuc.edu> > Cc: > Sent: Saturday, June 11, 2011 12:22 PM > Subject: [LLVMdev] Build of C++ project with clang++ fails (local symbol 1: discarded in section `xxx') > >

Have you sent the patch, with a descriptive header, to the llvm-commits list? On Oct 2, 2012, at 12:33 AM, Yuri <yuri at rawbw.com> wrote: > On 07/05/2012 15:52, Yuri wrote: >> I think my patch fell through the cracks: >> http://llvm.org/bugs/show_bug.cgi?id=13163 >> >> Could anybody please check it in? >> > > Could anybody please review and check

> On 2015-Jun-01, at 11:06, Reid Kleckner <rnk at google.com> wrote: > > I'm pretty sure module linking is expected to occur in the same LLVM context. Correct. > IIRC Duncan had some proposal for how ld64 could do something clever with multiple contexts, but I've totally forgotten what it was. This was for LTO (probably unrelated to Yuri's scenario?). 1.

In r134967 it still worked, and in r137742 it now doesn't. I used such flags: --enable-assertions --enable-shared --enable-libffi --enable-debug-runtime --enable-debug-symbols --disable-optimized Before build would create directory tools/llvm-shlib under the build tree. Now it is missing. Yuri

On Feb 19, 2011, at 8:05 PM, Yuri wrote: > On 02/19/2011 14:52, Yuri wrote: >> Will MC path for JNI be included in 2.9? >> > > Sorry. I meant: Will MC path for JIT be included in 2.9? While it would be nice, it doesn't seem like anyone is working on it at the moment. -Chris