News for hackers. Stuff that matters.

A comment on ARMv7 vs. x86-64: Pathfinding benchmark of C++, D, Go, Nim, Ocaml, and more. Parent comment

Re:ARMv7 vs. x86-64: Pathfinding benchmark of C++, D, Go, Ni... by logicchains on Saturday December 20, 2014 @07:57AM (#8776526)
It's in the makefile in that repo:

    	g++ cpp.cpp -std=c++11 -Wall -O2 -march=native -o cpp
I was originally using -O3 but then someone found that -O2 is actually faster in this case.
[ Parent | on HN ]
Re:ARMv7 vs. x86-64: Pathfinding benchmark of C++, D, Go, Ni... by vmarsy on Saturday December 20, 2014 @02:50PM (#8777686)
When visited was changed from a vector<bool> to a bitset<T>, why is it not passed by reference anymore?
[ Parent | on HN ]
Re:ARMv7 vs. x86-64: Pathfinding benchmark of C++, D, Go, Ni... by pbsd on Saturday December 20, 2014 @05:05PM (#8778107)
The most common call in the benchmark is to `getLongestPath<16>`. Passing 16 bits by value is cheaper and easier for the compiler to optimize (i.e., no aliasing) than passing by reference. I'd expect graphs with many nodes to behave differently.
[ Parent | on HN ]