search for: setbuffers

Hello, I'm trying samba-2.0.6 on my Sony NEWS-OS 4.2.1aRD which is based on 4.3BSD, having trouble with compilation. Also I have question and want be helped to solve the problem. Yes, I can compile it with dirty hack which is found at ftp://ftp.tutrp.tut.ac.jp/pub/sony-news/samba/samba-news4.diff There are some problems about this old and specific system. 1. It does not have setvbuf(). 2.

+update diff 2015-05-02 7:38 GMT+03:00 Yaron Keren <yaron.keren at gmail.com>: > I outlined (is that the right > word?) raw_char_ostream::grow, raw_char_ostream::write (both) into > raw_ostream.cpp with less than 10% difference in performance. > > Profiling reveals that the real culprit is the code line > > OS.reserve(OS.size() + 64); > > called from

Could you dig into why: + raw_ostream &write(unsigned char C) override { + grow(1); + *OutBufCur++ = C; + return *this; + } Is 3 times as fast as raw_svector_ostream? I don't see a good reason why that should be any faster than: raw_ostream &operator<<(char C) { if (OutBufCur >= OutBufEnd) return write(C); *OutBufCur++ = C; return *this; }

I don't think we should make flush virtual. Why do you need to do it? Can't you set up the base class to write to use the tail of the memory region as the buffer? On 24 April 2015 at 06:46, Yaron Keren <yaron.keren at gmail.com> wrote: > Hi, > > Is this what you're thinking about? > The code is not tested yet, I'd like to know if the overall direction and >

Hello, Just an update on that. I am personally using -git-commit-after-all *as-is* extremely frequently (combined with "git filter-branch" and "opt -S -instnamer" it is extremely useful). I unfortunately won't have time to write a better implementation of that, and I agree "git fast-import" seems the way to go. If anybody is motivated enough to do so, feel free.

A very common code pattern in LLVM is SmallString<128> S; raw_svector_ostream OS(S); OS<< ... Use OS.str() While raw_svector_ostream is smart to share the text buffer itself, it's inefficient keeping two sets of pointers to the same buffer: In SmallString: void *BeginX, *EndX, *CapacityX In raw_ostream: char *OutBufStart, *OutBufEnd, *OutBufCur Moreover, at runtime the

Oh, well... as usually the answer appears to be pretty obvious. 99% of the time is spent inside the plain write. -print-after-all prints into llvm::errs(), which is an *unbuffered* raw_fd_stream. And -git-commit-after-all opens a *buffered* raw_fd_stream. As soon as I hacked -print-after-all to use a buffered stream to stderr performance went up to the normal expected values: ] time bin/opt

Sean, thanks for reminding this, Alp did commit a class derived from raw_svector_ostream conatining an internal SmallString he called small_string_ostream. The commit was reverted after a day due to a disagreement about the commit approval and apparently abandoned. http://lists.cs.uiuc.edu/pipermail/llvm-commits/Week-of-Mon-20140623/223393.html

Here's a performance testcase for the raw_svector_ostream patch. On my WIndows x64 machine it runs in 1010ms with the current code and in 440ms with the patch applies. Is this OK to commit? 2015-05-02 21:31 GMT+03:00 Yaron Keren <yaron.keren at gmail.com>: > Following a hint from Duncan in http://llvm.org/pr23395, here is a > revised patch. Rather then introduce the

Could this be why I am getting a problem with the initial configure? checking for Active Directory and krb5 support... yes checking for ldap_initialize... (cached) no configure: error: Active Directory support requires ldap_initialize -------------- next part -------------- SAMBA VERSION: 3.2.0 LIBREPLACE_LOCATION_CHECKS: START checking build system type... sparc-sun-solaris2.9 checking

> FWIW: We could also just have a mode that dumps 1 file per pass. That is enough to make it convenient/easy to run diff between passes. (And if you wanted to you could still > make a git repository out of it with an external script). > > - Matthias I have done this before and would strongly encourage this approach as opposed to direct emission to std[out|err] or directly involving a

The Wine development release 1.9.16 is now available. What's new in this release (see below for details): - Better 64-bit binary compatibility on macOS. - Performance improvements in JavaScript. - More progress towards the Direct3D command stream. - More shader instructions in Direct3D. - Performance improvements in GDI. - Various bug fixes. The source is available from the

I am trying to compile samba 4 with solaris 10 on a x86 machine. I get the "checking configure summary... configure: error: summary failure. Aborting config" failure. I am using gcc 3.4.3 Here is how it goes: cowabunga: /export/home/test/samba4/source$ ./autogen.sh ./autogen.sh: running script/mkversion.sh ./script/mkversion.sh: svn: not found ./script/mkversion.sh: svn: not found

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I have recently tried to build samba4 on osx from the latest git pull I have had a build error while trying to compile this. I have make clean, and reconfigured this. [ 480/2253] Compiling lib/ldb/common/ldb.c ../lib/ldb/common/ldb.c: In function ?ldb_init?: ../lib/ldb/common/ldb.c:103: warning: ?tevent_loop_allow_nesting? is deprecated (declared

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, I have just pulled the latest git on my OSX 10.6.4 install. I am attempting to build samba4 and i get this error. [ 411/2152] Compiling ../lib/tdb/common/transaction.c ../../lib/tdb/common/transaction.c: In function ?transaction_sync?: ../../lib/tdb/common/transaction.c:552: error: implicit declaration of function ?fdatasync? Waf: Leaving

Hello there, I encountered an error with Samba3.0 installation. I'm sending it as an attachment(i.e. whatever appeared at "konsole") So, please help me out to install Samba3.0 on RedHat Linux 8.0 Waiting For reply !!! Aditya R. Gupta [Beta] HelpClick onthe image to chat with me -------------- next part -------------- [root@localhost root]# cd

Is smbtorture a simple SMB client that is completely separate from Samba server? (I.e., can I use it to test, e.g., a regular Windows SMB server?) Or is it something that only tests Samba server? Anyway, I haven't had any luck compiling it. Any hints? Here is a transcript (this is on SUSE Linux Enterprise 9): cwu@cham6:~/tmp/apps/samba-3.0.14a/source> ./configure

Hi All, I'm having problems compiling a newer version of samba (3.3.x or 3.4.x) on solaris 9. We are currently running 3.0.23d and have been putting off upgrading for far to long. I've tried gcc and sun studio 12 cc with the same issues when it comes to compiling dbwrap.c. I can't seem to find anything on google that's related to my issue. Here's my configure line when

Hopefully someone can hep. I am trying to compile Samba 3.0.4 on AIX 5.2 with AD Support. The problem is that it compiles fine but does a core dump when it's use is attempted. Several of the configuration usability parameters are showing NO. Expecially the CoreFoundation, fcntl, and syscall related areas. I need help determining what my problem is, and is there a place where I can find a

Hopefully someone can hep. I am trying to compile Samba 3.0.4 on AIX 5.2 with AD Support. The problem is that it compiles fine but does a core dump when it's use is attempted. Several of the configuration usability parameters are showing NO. Expecially the CoreFoundation, fcntl, and syscall related areas. I need help determining what my problem is, and is there a place where I can find a