Well, reporting back. I got it to compile by specifying -msse and -msse2 to gcc when compiling. I first was hashing about 692kh/s (50% of SVN r130[1400kh/s]) but recompiled and am now receiving about ~1120kh/s. This is currently the equivalent of using both of my CPUs without HyperThreading, though I […]

Looks like we’re triggering a compiler bug in the tree optimizer. Can you try to compile it -O0? MinGW GCC 4.5.0: Crypto++ doesn’t work, X86_SHA256_HashBlocks() never returns I only got 4-way working with test.cpp but not when called by BitcoinMiner MinGW GCC 4.4.1: Crypto++ works 4-way SIGSEGV GCC is definitely […]

Looks like we’re triggering a compiler bug in the tree optimizer. Can you try to compile it -O0? Got the test working on 32-bit with MinGW GCC 4.5.  Exactly 50% slower than stock with Core 2. Related posts: Re: 4 hashes parallel on SSE2 CPUs for 0.3.6 If you haven’t […]

If you haven’t already, try aligning thash.  It might matter.  Couldn’t hurt. Quote from: tcatm on August 14, 2010, 00:53:07 Looks like we’re triggering a compiler bug in the tree optimizer. Can you try to compile it -O0? No help from -O0, same error. MinGW is GCC 3.4.5.  Probably the […]

Just a question for whoever, trying to wrap up the information in this thread. Does this: 1. Work on 32-bit? 2. Patch the SVN (r130 as of current) or Git? 3. Compile on CentOS? If anyone has any answers I would greatly appreciate them. MinGW on Windows has trouble compiling […]

Quote from: jgarzik on August 13, 2010, 20:13:30 What happens when we desire to return additional information, beyond tx-id? For the sake of future compatibility, it seems like the flag should present a choice between returning (a) just the current ‘sent’, or (b) a JSON map containing tx-id, and perhaps […]

[…] Yes, I am talking about the hypothetical system. The way I proposed the system, each time a block gets generated every validating node must accept or reject that block by validating the transactions and confirming the hashes in the block. In effect, the same work that is being done […]

Here’s a test build if you’d like to help test before 0.3.9 is released. (or if you’d rather get upgrading out of the way now instead of waiting) Downloads:  (binaries only) http://www.bitcoin.org/download/bitcoin-0.3.9.rc1-win32.zip (http://www.bitcoin.org/download/bitcoin-0.3.9.rc1-linux.tar.gz) SHA1 a36ea00cce27b4b083755df73a3d1e5e5729884e bitcoin-0.3.9.rc1-win32.zip SHA1 bbb333b0ea57302740ad1bb9948520d00f884f9d bitcoin-0.3.9.rc1-linux.tar.gz Edit: Linux please test rc2 instead.  This adds a -4way switch […]

Quote But there will be no irc server to bootstrap from. Which doesn’t matter because you can’t access sourceforge to download the software either. If you’ve ever been connected before, you don’t need IRC to bootstrap anymore.  Even if you haven’t, you can bootstrap from seed nodes.  IRC is completely […]

So, -paytxfee sets nTransactionFee. Can someone explain how nTransactionFee causes a client to behave? And more specifically, what happens when node A sets 1000.0 and all other nodes use 0.01? No, that’s not what it is. -paytxfee allows you to include a transaction fee with your transactions.  If transaction confirmations […]