search for: open64

...te. gcc -I../../src/extra/zlib -I../../src/extra/bzip2 -I../../src/extra/pcre -I. -I../../src/include -I../../src/include -I/usr/local/include -DHAVE_CONFIG_H -g -O2 -c connections.c -o connections.o connections.c: In function `init_con': connections.c:381: structure has no member named `open64' connections.c: In function `newfile': connections.c:639: structure has no member named `open64' connections.c: In function `newfifo': connections.c:785: structure has no member named `open64' connections.c: In function `do_fifo': connections.c:837: structure has no member n...

Hi, I have been working towards developing compiler optimization tools targeting multi core processors while using LLVM IR as the starting point and building on top of the analysis and optimization passes available in the llvm source. Recently, I looked into Open64 and its intermediate representation WHIRL. Documentation for developers to use Open64 seems to be inadequate (when compared to LLVM documentation). I am planning to download the source and look into it. I was wondering if anyone has worked with both LLVM and Open64 and has some qualitative compari...

Hi, Arvind Sudarsanam: I know some of Open64. Above all, Open64 is designed for a high performance compiler. It is now supported by AMD, HP, ICT Chinese Academy of Science, etc. and has been ported to X86, Itanium, Loongson CPU etc. And to your questions 1, Open64 already have some main optimization phases, Inline for aggressive inline opt....

On 11/08/2013 09:12 AM, Steve Capper wrote: > diff --git a/usr/klibc/open64.c b/usr/klibc/open64.c > new file mode 100644 > index 0000000..6ca603e > --- /dev/null > +++ b/usr/klibc/open64.c > @@ -0,0 +1,22 @@ > +/* > + * open64.c > + * > + * For 64 bit systems without the open syscall, pass straight > + * through into openat. > + */ > +...

Hi, Gang: I remember there were different voices when you check-in the code. I agree with them although I didn't reply your mail in open64's mailing list. In the transformation you illustrate, it involves two operations: 1) promote WHILE-loop into DO-loop (i.e noncountable loop to countable loop) 2) get rid of trip-count dec/inc and compare. 1) is irrelevant to HW loop. Any scalar optimizer should handle 1). It is n...

Hi, All: Is it legal to delete empty infinite loop like this : "while(1) {}"? It is interesting that both llvm and gcc keep the loop, however Open64 delete it. If it is safe to delete this loop, it would be lot easier to delete non-obvious dead loop like following as compiler doesn't need to prove if the loop in question is infinite or not. Currently llvm is not able to delete such dead loop. while (a) { a = whatever } ; // no...

...lidity check functionality , but the code reduced, more stable. Gang 在 2012-11-23，3:17，Shuxin Yang <shuxin.llvm at gmail.com> 写道： > Hi, Gang: > > I remember there were different voices when you check-in the code. > I agree with them although I didn't reply your mail in open64's mailing list. > > In the transformation you illustrate, it involves two operations: > 1) promote WHILE-loop into DO-loop (i.e noncountable loop to countable loop) > 2) get rid of trip-count dec/inc and compare. > > 1) is irrelevant to HW loop. Any scalar optimizer...

Hi all, We did some benchmarks on code size with clang, gcc 4.5, and open64. Clang performed second in the test. The benchmark is CSiBE. Clang can't compile the linux kernel (some inline asm not supported) and replaypc (error: use of unknown builtin '__builtin_next_arg'). The concrete results are attached. -------------- next part -------------- An HTML attachm...

I am the designer for open64 hwloop structure, but I am not a student. Hope the following helps: To transform a loop into hwloop, we need the help from optimizer. For example, while(k3>=10){ sum+=k1; k3 --; } into the form: zdl_loop(k3-9) { sum+=k1; } So, we introduce a new ZDLBR whirl(open64...

...rogram > optimization (http://gcc.gnu.org/wiki/LinkTimeOptimization). Hi, Diego: Thank you for the comment. Quite honestly, I'm not very familiar with gcc's LTO implementation, and now I'm not allowed to read any GPL V3 code. What I'm describing here is somewhat similar to Open64's IPA implementation. I did port gcc before and of course read its document . Based on my little knowledge of its internal, I think gcc's "whole-program" mode is almost identical to Open64's IPA in spirit, I guess gcc community likely borrowed some idea from Open64. On the...

...handler/logfiles", 0xFFBEDC88) = 0 stat64("run/data/fracas/hs-handler/logfiles", 0xFFBEEF70) = 0 stat64("run/data/fracas/hs-handler/logfiles/neuer ordner", 0xFFBEEF70) Err#2 ENOENT stat64("run/data/fracas/hs-handler/logfiles/neuer ordner", 0xFFBEEF70) Err#2 ENOENT open64("run/data/fracas/hs-handler/logfiles", O_RDONLY|O_NDELAY) = 25 fcntl(25, F_SETFD, 0x00000001) = 0 fstat64(25, 0xFFBEE118) = 0 getdents64(25, 0x0029A5D0, 1048) = 896 getdents64(25, 0x0029A5D0, 1048) = 88 getdents64(25, 0x0029A5D0, 1048) = 0 close(25) = 0 stat64("run/data/f...

...page back with an error messages), nor when I change the password of an existing samba user, or whatever. On the Solaris box, I can find a core file in the swat directory. If I truss (see the system calls) the inetd process and its childs, I see at the end: ...[27542 is the swat PID]... 27542: open64("/usr/local/samba/private/smbpasswd", O_RDONLY) = 5 27542: sigaction(SIGALRM, 0xEFFFEF98, 0x00000000) = 0 27542: alarm(5) = 300 27542: fcntl(5, F_SETLKW64, 0xEFFFF0A8) = 0 27542: alarm(0) = 5...

On Tue, Nov 13, 2012 at 11:23:02PM -0800, Shuxin Yang wrote: > Hi, All: > > Is it legal to delete empty infinite loop like this : "while(1) {}"? > It is interesting that both llvm and gcc keep the loop, however Open64 > delete it. I think it's illegal to delete such infinite loop, perhapes you should file a bug report to open64. That's my 2 cents. Regards, chenwj -- Wei-Ren Chen (陳韋任) Computer Systems Lab, Institute of Information Science, Academia Sinica, Taiwan (R.O.C.) Tel:886-2-2788-3799 #...

...re entering into the codegen. Looking at its > implementation, > >it. > > Could you please articulate why CG fail to recognize it? Well, just because the loop unrolling pass runs before the CG is called. > I remember in gcc, recognizing hw loop is in a RTL pass, and in > Open64, one > student(?) added some stuff in Scalar Opt, instead of CodeGen, just > for HW loop. > I recalled there is only one reason sounds valid -- prevent the loop > become > too big to fit in HW constraint. It sounds very similar to our implementation. We've implemented the hw...

Hi, Gang: I don't want to discuss Open64 internal in LLVM mailing list. Let us only focus on the design per se. As your this mail and your previous mail combined give me a impression that : The only reason you introduce the specific operator for HW loop in Scalar Opt simply because you have hard time in figure out the trip count...

https://bugzilla.samba.org/show_bug.cgi?id=1536 ------- Additional Comments From wayned@samba.org 2004-07-30 13:30 ------- Created an attachment (id=589) --> (https://bugzilla.samba.org/attachment.cgi?id=589&action=view) Add checks for open64 and mkstemp64 to configure If the user's system has open64() but not mkstemp64(), we avoid using mkstemp(). -- Configure bugmail: https://bugzilla.samba.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA...

...PM +0800, 陳韋任 (Wei-Ren Chen) wrote: > On Tue, Nov 13, 2012 at 11:23:02PM -0800, Shuxin Yang wrote: > > Hi, All: > > > > Is it legal to delete empty infinite loop like this : "while(1) {}"? > > It is interesting that both llvm and gcc keep the loop, however Open64 > > delete it. > > I think it's illegal to delete such infinite loop, perhapes you should > file a bug report to open64. That's my 2 cents. The reason I think it's illegal is because if you remove it, then the behavior is different. One with infinite empty loop wil...

Hello, We are currently evaluating LLVM as a compiler technology against Open64 and have a few questions regarding its currently status with respect to optimizations in particular. Control flow is often expensive on the architectures we are considering and as such loop optimizations, e.g. unroll and jam, can play an important role. For example, consider the following prog...

...ot; in SQL. I changed default_pass_scheme from CRYPT to PLAIN, and no troubles. I then tried dovecotpw: dovecotpw -p 123 -s PLAIN-MD5 {PLAIN-MD5}202cb962ac59075b964b07152d234b70 dovecotpw -p 123 -s CRYPT Segmentation Fault (core dumped) So I then tried this: truss dovecotpw -p 123 -s crypt open64("/dev/urandom", O_RDONLY) = 3 read(3, "F80E82 c", 4) = 4 fcntl(3, F_GETFD, 0x00000000) = 0 fcntl(3, F_SETFD, 0x00000001) = 0 open64("/usr/local/lib/dovecot/auth/password", O_RDONLY|O_NDELAY) Er...

...NIL NIL "base64" 801726 10279)) A truss of the process reveals: write(1, " * 4 0 F E T C H (".., 36) = 36 sendfilev64(1, 1, 0xFFBFF2C0, 1, 0xFFBFF2B4) = 65536 close(10) = 0 close(8) = 0 open64("/var/qmail/maildirs/09/44/XXXXXX/Maildir/maildirsize", O_RDWR|O_APPEND) = 8 read(8, " 1 0 4 8 5 7 6 0 S\n 6 4".., 5120) = 1188 read(8, 0xFFBFE3FC, 3932) = 0 write(1, " )\r\n 0 0 0 0 0 0 1 0 ".., 33) = 33 pollsys(0x000B0378, 3, 0xFFBFF8...