search for: popizdeh

Displaying 20 results from an estimated 74 matches for "popizdeh".

2011 Sep 07
2
[LLVMdev] [cfe-dev] Unicode path handling on Windows
On Tue, Sep 6, 2011 at 11:28 PM, Nikola Smiljanic <popizdeh at gmail.com> wrote: > The problem is not in the functions that return multibyte strings (the > multibyte string is coming from argv) argv is implicitly the return from a UTF16->multibyte conversion (i.e. it's lossy). -Eli
2011 Sep 07
2
[LLVMdev] [cfe-dev] Unicode path handling on Windows
On Wed, Sep 7, 2011 at 12:20 AM, Nikola Smiljanic <popizdeh at gmail.com> wrote: > So what are you exactly saying? Somebody proposed using GetCommandLine > instead of using argv directly. And what about my other points about ::open > and ::stat? Because of the way Windows works, the only fully correct solution is to never touch the native chars...
2011 Sep 07
0
[LLVMdev] [cfe-dev] Unicode path handling on Windows
...t are you exactly saying? Somebody proposed using GetCommandLine instead of using argv directly. And what about my other points about ::open and ::stat? On Wed, Sep 7, 2011 at 8:52 AM, Eli Friedman <eli.friedman at gmail.com> wrote: > On Tue, Sep 6, 2011 at 11:28 PM, Nikola Smiljanic <popizdeh at gmail.com> > wrote: > > The problem is not in the functions that return multibyte strings (the > > multibyte string is coming from argv) > > argv is implicitly the return from a UTF16->multibyte conversion (i.e. > it's lossy). > > -Eli > --------------...
2011 Oct 12
1
[LLVMdev] [cfe-dev] Unicode path handling on Windows
...mmit (I'm guessing that you don't have commit access)? cfe-commits is in the CC. On Tue, Oct 11, 2011 at 6:55 PM, Aaron Ballman <aaron at aaronballman.com>wrote: > Looks good to me! > > Thanks! > > ~Aaron > > On Tue, Oct 11, 2011 at 2:26 AM, Nikola Smiljanic <popizdeh at gmail.com> > wrote: > > Fixed formatting. > > > > On Mon, Oct 10, 2011 at 9:13 PM, Aaron Ballman <aaron at aaronballman.com> > > wrote: > >> > >> I would still fix the code formatting even though you merely > >> uncommented it (just...
2011 Nov 09
2
[LLVMdev] [cfe-dev] LLVM 3.0rc3 Testing Beginning
Nikola Smiljanic <popizdeh at gmail.com> writes: > I'm not sure if this makes a difference but I ran this > > make -j 2 -k LLVMCC_OPTION=clang ENABLE_BUILT_CLANG=1 ENABLE_PARALLEL_REPORT=1 TEST=simple report > ../../report.txt 2>&1 That does indeed seem to get me further. Thanks!...
2015 Jul 21
2
[LLVMdev] [3.7 Release] RC1 has been tagged, Testing Phase I begins
...#39;s called i586, not i686 :-( >> >> +Alexey: do you think we can handle this in the compiler-rt cmake >> files somehow? Maybe try targeting both i686 and i586 unless that >> would break something else? >> >> On Fri, Jul 17, 2015 at 1:31 AM, Nikola Smiljanic <popizdeh at gmail.com> >> wrote: >> > CMake Error at projects/compiler-rt/cmake/config-ix.cmake:125 (message): >> > Cannot compile for i686 >> > >> > CMakeError.log attached, seems like #include checks are failing? This >> is x86 >> > openSUSE. &gt...
2011 Sep 07
2
[LLVMdev] [cfe-dev] Unicode path handling on Windows
As was mentioned once before, the correct solution is to never use multibyte anywhere. Any Windows functions that currently return multibyte strings should be converted to their wide-string (unicode) equivalent, with the result converted to UTF-8. > From: Nikola Smiljanic <popizdeh at gmail.com> > > I think I got it this time. I realized that ::open and ::stat work just fine with multibyte paths on windows so there's no need to change this code. The only problem is llvm::sys::fs module which falsely assumes that input strings are UTF8 encoded when they are in fac...
2015 Feb 26
2
[LLVMdev] [3.6 Release] RC4 has been tagged
I still haven't finished but I don't think you have to wait. On Fri, Feb 27, 2015 at 7:46 AM, Renato Golin <renato.golin at linaro.org> wrote: > We got everything, haven't we? > > On 26 February 2015 at 20:44, Nikola Smiljanic <popizdeh at gmail.com> wrote: > > Final has been tagged, I think we're about to release it. > > > > On Fri, Feb 27, 2015 at 7:43 AM, Hayden Livingston < > halivingston at gmail.com> > > wrote: > >> > >> Are we waiting for an RC5? It seems like the re...
2011 Sep 20
0
[LLVMdev] [cfe-dev] Unicode path handling on Windows
...patch where I tried this (it has a number of issues but I'd like to hear from someone that this solution makes sense before I try to address them). On Wed, Sep 7, 2011 at 9:39 AM, Eli Friedman <eli.friedman at gmail.com> wrote: > On Wed, Sep 7, 2011 at 12:20 AM, Nikola Smiljanic <popizdeh at gmail.com> > wrote: > > So what are you exactly saying? Somebody proposed using GetCommandLine > > instead of using argv directly. And what about my other points about > ::open > > and ::stat? > > Because of the way Windows works, the only fully correct solution...
2014 Dec 13
5
[LLVMdev] 3.5.1 Testing Phase Begins
You're not the only one Hans, my VMs have started crashing my host OS :) Fedora and OpenSUSE look good, binaries uploaded. On Sat, Dec 13, 2014 at 12:06 PM, Hans Wennborg <hans at chromium.org> wrote: > > On Thu, Dec 11, 2014 at 5:26 PM, Tom Stellard <tom at stellard.net> wrote: > > Hi, > > > > 3.5.1-rc1 has been tagged, so it is time to begin testing. We
2011 Sep 07
0
[LLVMdev] [cfe-dev] Unicode path handling on Windows
...tioned once before, the correct solution is to never use > multibyte anywhere. Any Windows functions that currently return multibyte > strings should be converted to their wide-string (unicode) equivalent, with > the result converted to UTF-8. > > > > From: Nikola Smiljanic <popizdeh at gmail.com> > > > > I think I got it this time. I realized that ::open and ::stat work just > fine with multibyte paths on windows so there's no need to change this code. > The only problem is llvm::sys::fs module which falsely assumes that input > strings are UTF8 enc...
2011 Oct 11
2
[LLVMdev] [cfe-dev] Unicode path handling on Windows
Fixed formatting. On Mon, Oct 10, 2011 at 9:13 PM, Aaron Ballman <aaron at aaronballman.com>wrote: > I would still fix the code formatting even though you merely > uncommented it (just to be consistent with the rest of the code). But > functionally-speaking, I think your patches are good. > > ~Aaron > -------------- next part -------------- An HTML attachment was
2011 Oct 11
0
[LLVMdev] [cfe-dev] Unicode path handling on Windows
Looks good to me! Thanks! ~Aaron On Tue, Oct 11, 2011 at 2:26 AM, Nikola Smiljanic <popizdeh at gmail.com> wrote: > Fixed formatting. > > On Mon, Oct 10, 2011 at 9:13 PM, Aaron Ballman <aaron at aaronballman.com> > wrote: >> >> I would still fix the code formatting even though you merely >> uncommented it (just to be consistent with the rest of the co...
2015 Feb 26
0
[LLVMdev] [3.6 Release] RC4 has been tagged
On 26 February 2015 at 20:48, Nikola Smiljanic <popizdeh at gmail.com> wrote: > I still haven't finished but I don't think you have to wait. No, that's ok. I'm not in a hurry. :)
2011 Nov 10
0
[LLVMdev] [cfe-dev] LLVM 3.0rc3 Testing Beginning
greened at obbligato.org (David A. Greene) writes: > Nikola Smiljanic <popizdeh at gmail.com> writes: > >> I'm not sure if this makes a difference but I ran this >> >> make -j 2 -k LLVMCC_OPTION=clang ENABLE_BUILT_CLANG=1 ENABLE_PARALLEL_REPORT=1 TEST=simple report > ../../report.txt 2>&1 > > That does indeed seem to get me further....
2011 Sep 01
3
[LLVMdev] [cfe-dev] Unicode path handling on Windows
...st literal[] = "俺です、俺俺"; //////// The include path (#include) should be handled as host-dependent. The literal should be interperted with input-charset and be emitted with exec-charset. Too hard the life is. Would you like to live in Japan? :p ...Takumi 2011/9/1 Nikola Smiljanic <popizdeh at gmail.com>: > The function available in clang/lib/Basic/ConvertUTF.c deals with unsigned > shorts, and I need wchar_t? > > On Thu, Sep 1, 2011 at 9:36 AM, Jean-Daniel Dupas <devlists at shadowlab.org> > wrote: >> >> Le 31 août 2011 à 21:02, Aaron Ballman a écr...
2015 Jul 17
2
[LLVMdev] [3.7 Release] RC1 has been tagged, Testing Phase I begins
Seems on OpenSUSE x86, it's called i586, not i686 :-( +Alexey: do you think we can handle this in the compiler-rt cmake files somehow? Maybe try targeting both i686 and i586 unless that would break something else? On Fri, Jul 17, 2015 at 1:31 AM, Nikola Smiljanic <popizdeh at gmail.com> wrote: > CMake Error at projects/compiler-rt/cmake/config-ix.cmake:125 (message): > Cannot compile for i686 > > CMakeError.log attached, seems like #include checks are failing? This is x86 > openSUSE. > > On Fri, Jul 17, 2015 at 9:14 AM, Hans Wennborg <hans...
2012 Jan 17
1
[LLVMdev] [cfe-dev] LLVM & Clang file management
On Sat, Dec 24, 2011 at 9:52 AM, Nikola Smiljanic <popizdeh at gmail.com> wrote: > > On Tue, Dec 6, 2011 at 11:27 AM, Manuel Klimek <klimek at google.com> wrote: >> >> >> Are there open bugs? A quick search for unicode on llvm.org/bugs >> didn't show anything windows specific. >> > > There's http://...
2011 Sep 20
2
[LLVMdev] [cfe-dev] Unicode path handling on Windows
On Tue, Sep 20, 2011 at 4:15 PM, Nikola Smiljanic <popizdeh at gmail.com> wrote: > OK since this approach makes sense I'll shoot with my questions :) > 1. Where should get_utf8_argv go and is the name of this function OK? Right > now the function is inside llvm::sys::fs namespace because I need access to > Windows.h, should I leave it the...
2012 Jun 13
2
[LLVMdev] [cfe-dev] Ninja build available for Visual Studio users
Wow, this is seriously fast on Windows! I've been using Ninja on Linux/Mac for awhile now, I'm glad to see it working on Windows now. On Wed, Jun 13, 2012 at 5:09 PM, =?utf-8?Q?=C3=93scar_Fuentes?= < ofv at wanadoo.es> wrote: > Nikola Smiljanic <popizdeh at gmail.com> writes: > > > Could somebody please provide more info. What exactly is ninja (I'm > > guessing it's a build system) and how to set it up in combination with > > Visual Studio? > > This is the message I posted on the LLVM mailing list. Here it goes...