Contact
If you have any ideas or questions, please feel free to contact us using our contact data or the form below.
Latest Articles
Back in 2010, security researcher Ron Bowes wrote a Ruby script that downloads information from Facebook's user directory, a searchable index of public profile pages. The directory did not expose a user's entire profile and
Many notebooks on the market feature switchable graphics, that is, a notebook with an Intel CPU with built-in HD Graphics technology, as well as an additional AMD HD Radeon GPU or nVidia GeForce GPU. During normal usage, just
The article related to multi-threading and SSE2 optimizations (you can find it here) uses a quick-and-dirty way to check if the optimized code is correct, i.e. it runs an iteration on a given input image with a reference serial
Different types of parallel loops with Intel TBB, SSE2, SSSE3 and Visual C++ 2012 22 April 2013, 22.15 Multi-thread
This is not the first article on this site that discusses how to use the Intel Thread Building Blocks library to spread the computation of an image-processing kernel over multiple threads: the article named "Multi thread loops
In a previous article named "Easy multi-thread programming Delphi", the AsyncCalls library was used to process multiple images at the same time. However, the processing of every single image was still strictly serial, even if
Latest Downloads
AltaPixShare
TBB Demo with Visual C++ 2012By WA Seattle SEO
| DelphiFeeds.com |
| All Delphi blogs directly from DelphiFeeds.com |
| The Register |
| Biting the hand that feeds IT — sci/tech news and views for the world |
Although the author takes all possible care to ensure the correctness of published information, no warranty can be accepted regarding the correctness, accuracy, up-to-dateness, reliability and completeness of the content of this information. The author expressly reserves the right to change, to delete or temporarily withdraw the contents completely or partly at any time and without giving notice. Liability claims against the author because of tangible or intangible damage arising from accessing, using or not using the published information, through misuse of the connection or as a result of technical breakdowns are excluded.