I wonder if it is not more useful to talk in terms of C11 features. Unlike
C99, C11 makes VLAs optional via __STDC_NO_VLA__, so you have a
standardized way of expressing the subset of C11 that is compatible with
C++11. __STDC_NO_ATOMICS__ and __STDC_NO_THREADS__ play a similar role.
Of course, s
Hi Shri,
Probably the best way to understand what is going on is to step through
things using a debugger, as Junchao suggests. VecAXPY does get used in a
lot of places, and maybe it is being called on some vectors that aren't
getting their type from the options database? Also, there are severa
You should read the CORAL RFPs. A guiding principle in both CORAL-1 and
CORAL-2 was for LLNL to buy the same machine as either Argonne or Oak Ridge.
In any case, you’ve got this precisely backwards. LLNL is getting a
supercomputer for the NNSA mission, as had been true of NNSA since the dawn
of th
Hi, Shri,
I don't understand either. But there are many invocations of VecAXPY etc.
Is it possible some are done on CPU? Attach a debugger and set a breakpoint
on VecAXPY_SeqCUDA to see if it gets a hit. If yes, then see why.
--Junchao Zhang
On Tue, Mar 10, 2020 at 2:44 PM Abhyankar, Shrirang
Hello all,
I need help in understanding the output from -log_summary for the GPU related
columns. I am currently simply setting -vec_type seqcuda which I believe
performs the vector operations on the GPU. With -vec_type seqcuda, I presumed
all vector operations are being done on the GPU. So, o
