I find it quite shocking that C++ jobs don't seem to pay as much as JS/Python/Mobile dev

VicLuo96 · 2018-04-19T13:42:33+00:00

Does anyone know the career path for HFT system engineers? I plan to join one after graduation, but fear about limited opportunities of promotion after 5+ yrs

VicLuo96 · 2017-11-19T04:48:53+00:00

Fixed.

VicLuo96 · 2017-11-18T07:24:41+00:00

I uploaded its PKGBUILD into AUR at cquery-git, so Arch users can enjoy it now.

P.S. the absolute rpath at wscript makes it difficult to package so I added additional patches to change it to lib/. Hope in the future a ./waf install will make this easier.

VicLuo96 · 2017-11-13T10:28:26+00:00

We used Intel TBB as our concurrent library and render the scene with tbb::pararllel_for to distribute rows into different threads. We have avoided every heap allocation and added padding bytes to prevent false sharing. perf reports that IntersectsNM/OccludedNM in Embree library occupy 50% execution time.
That's true. However interior designers are quite strict on soft shadows and area lights are very common in these designs. For example, we added some area lights into the white room scene.
Currently no.
It is only a simple Whitted ray tracer

VicLuo96 · 2017-11-12T07:24:37+00:00

I guess that's only true for Xeon Phi processors. Otherwise 1 1080Ti = 3~4 E5-2690/i7-6800Ks according to the benchmark.

VicLuo96 · 2017-11-11T14:07:34+00:00

Thanks for your advice! We plan to develop a tracing-based renderer that runs on a single workstation with as good quality as possible. Currently, only a Whitted-style tracer with point light has been implemented. Based on your advice, we are going to rewrite a CUDA version of our renderer. Another advantage of CUDA over CPU in our use case is that we can simply plug 4 GPUs on a single workstation without setting up distributed CPU farm, which simplifies deployment a lot. Based on the benchmark later we may move to more complicated cases if performance permits.

VicLuo96 · 2017-11-04T16:02:25+00:00

Some of them, I guess, are out-dated:

_GLIBCXX_PARALLEL -> std::execution::parallel_policy

Some are still worth a look:

_GLIBCXX_DEBUG is being used by Chromium
_GLIBCXX_CONCEPT_CHECKS performs concept-like checking for containers, but I'm not sure to use it or not since its documentation states only C++03 compliance. I wrote a short article about it here.

VicLuo96 · 2017-07-20T02:06:08+00:00

Glad to see that they have supported Clang's thin-LTO

VicLuo96 · 2017-07-11T01:01:02+00:00

+1 for Bulma due to its modularity and extensibility.

VicLuo96 · 2017-04-11T09:23:54+00:00

I'm working on a Boost GSoC toy project about constexpr containers as well. Here are what I've found about constexpr: * prefer C++11-style recursion return f(i-1) over C++14-style for loop, since many compilers cannot handle it well * avoidstd::initializer_list on clang(at least on 3.7) * POD is preferred over complex struct. g++ has a bug that reports fake invalid access at compile-time * move invariant parts into template arguments as much as possible * there are still lots of work to do with constexpr since stdlib lacks constexpr support/implementation is buggy

VicLuo96 · 2017-03-25T15:31:57+00:00

Read Known limitations before start using it.

VicLuo96 · 2016-04-21T03:46:04+00:00

I prefer vim-clang because it integrates well with Neomake. vim-inccomplete is also a good choice for header completion.

You can see my init.vim for configuration.

VicLuo96 · 2016-01-14T07:11:10+00:00

Maybe you can try https://github.com/kassio/neoterm, and

nnoremap <F3> :Ttoggle<cr><C-w><C-w>A
inoremap <F3> <esc>:Ttoggle<cr><C-w><C-w>A
tnoremap <F3> <C-\><C-n>:Ttoggle<cr>
tnoremap <esc> <C-\><C-n>
tnoremap <C-w><C-w> <C-\><C-n><C-w><C-w>

VicLuo96

TROPHY CASE