Android NDK Revision 10d available

By Razvan Pascalau | Dec 12, 2014 12:56 PM | Tags: ndk framework basics android

For all the people that develop for Android, a new version( revision 10d) of the Android Native Development Kit has been released.

Android NDK Revision 10d available

From the release log:

• Made GCC 4.8 the default for all 32-bit ABIs. Deprecated GCC 4.6, and will remove it next release. To restore previous behavior, either add NDK_TOOLCHAIN_VERSION=4.6 to ndk-build, or add --toolchain=arm-linux-androideabi-4.6 when executing make-standalone-toolchain.sh on the command line. GCC 4.9 remains the default for 64-bit ABIs.
• Stopped all x86[_64] toolchains from adding -mstackrealign by default. The NDK toolchain assumes a 16-byte stack alignment. The tools and options used by default enforce this rule. A user writing assembly code must make sure to preserve stack alignment, and ensure that other compilers also comply with this rule. (GCC bug 38496)
• Added Address Sanitizer functionality to Clang 3.5 support to the ARM and x86 ABIs. For more information on this change, see the Address Sanitizer project.
• Introduced the requirement, starting from API level 21, to use -fPIE -pie when building. In API levels 16 and higher, ndk-build uses PIE when building. This change has a number of implications, which are discussed in Developer Preview Issue 888. These implications do not apply to shared libraries.

And much more ...

In defense of printf -- Kenny Kerr

By ltorje | Dec 12, 2014 09:41 AM | Tags: None

To use or not to use cout instead of printf -- that is the question!

In case you missed Kenny Kerr's article on printf vs cout:

In defense of printf

From the article:

Folks seem to enjoy pointing out that I use printf in many of my examples of “modern C++”, as if printf is not really proper C++. Apparently, I should be using cout. The trouble is that cout isn’t exactly modern either...

Address and Thread Sanitizers in GCC -- Red Hat Developer Blog

By Marcin Hoppe | Dec 12, 2014 07:40 AM | Tags: gcc basics

A short article about two error-detection features in GCC:

Address and Thread Sanitizers in GCC

by Dodji Seketeli on Red Hat Developer Blog

From the article:

Since their 4.8 version, the C and C++ compilers of the GNU Compiler Collection are equipped with built-in memory and data race errors detectors named Address Sanitizer and Thread Sanitizer.

This article intends to quickly walk you through the highlights of these two interesting tools.

2014 LLVM Developers' Meeting: Slides & Videos

By Adrien Hamelin | Dec 11, 2014 10:48 PM | Tags: experimental advanced

Now available the presentation slides and videos of the LLVM Developers' Meeting that occured last october:

2014 LLVM Developers' Meeting: Slides & Videos

Notably can be found talks about security in the source code, the OpenMP implementation or optimizations to be made by the compiler, and many more.

Quick Q: What is noexcept useful for? -- StackOverflow

By Blog Staff | Dec 11, 2014 10:58 AM | Tags: None

Quick A: Guaranteeing "this function won't throw" enables optimization opportunities.

Recently on SO:

What is noexcept useful for?

I saw that c++11 added the noexcept keyword. But I don't really understand why is it useful.

If the function throws when it's not supposed to throw - why would I want the program to crash?

So when should I use it?

Also, how will it work along with compiling with /Eha and using _set_se_translator? This means that any line of code can throw c++ exception - because it might throw a SEH exception (Because of accessing protected memory) and it will be translated to c++ exception.

What will happen then?

A gotcha with ptr_vector -- Andrzej Krzemieński

By Felix Petriconi | Dec 10, 2014 08:34 AM | Tags: intermediate boost

Do you know Boost.Pointer Container? Andrzej gives some useful information in his recent blog entry:

A gotcha with ptr_vector

He gives answers to these questions:

What would you use boost::ptr_vector for? Why would you need to have a vector of pointers, which you want to delete yourself? Is it because:

1. You want the objects to remain at the same address even if you re-allocate the array under the vector?
2. You want to inter-operate with a library that already deals with owing pointers?
3. You want it to be faster than if you were storing values in std::vector?
4. You want the “polymorphic behavior” of your objects?

Property Testing in C++ -- Jeremy Wright

By Jordi Mon Companys | Dec 10, 2014 08:29 AM | Tags: None

In case you missed it, this may be midly controversial but we felt it could be of interest:

Property Testing in C++

by Jeremy Wright

From the article:

One might say tests are shiny. I don't know if they are really shiny as much as I found another cool use for uniform_int_distribution<>...

Qt 5.4 released --Lars Knoll

By Razvan Pascalau | Dec 10, 2014 08:23 AM | Tags: qt framework basic

A new major version of the Qt has been released.

Qt 5.4 released

From the news article:

I am happy to announce that Qt 5.4 has been released today and is available for download from qt.io. Together with Qt 5.4, we have also released Qt Creator 3.3 and an update to Qt for device creation on embedded Linux and embedded Android.

But let’s start with Qt 5.4. One of the main focus areas of this Qt release has been around Web technologies and we have a lot of cool new things to offer there...

Why Students Need the CppCat Code Analyzer -- Andrey Karpov

By Andrey Karpov | Dec 10, 2014 08:11 AM | Tags: None

Today on viva64:

Why Students Need the CppCat Code Analyzer

by Andrey Karpov

CppCat is a simple static code analyzer capable of detecting bugs in C/C++ programs. We started granting free academic licenses to all interested (students, teachers, and so on). For the sake of popularizing CppCat among students, I decided to write this post about errors that can be found in student lab work tasks posted at Pastebin.com...

Blaze 2.2 released

By Felix Petriconi | Dec 10, 2014 08:02 AM | Tags: performance

Blaze, an open-source, high-performance C++ math library for dense and sparse arithmetic, released their new version.