Wolfgang Bangerth

Confirmed. This is the backtrace: ``` Thread 1 "aspect" received signal SIGFPE, Arithmetic exception. dealii::VectorizedArray::operator+= (vec=..., this=0x55555af7a340) at /home/bangerth/p/deal.II/1/install/include/deal.II/base/vectorization.h:3341 3341 data += vec.data; (gdb) bt #0 dealii::VectorizedArray::operator+= (vec=..., this=0x55555af7a340) at...

This is outside my area of expertise, so I can not really help with what is going on. But this is what I find: ``` (gdb) list 3336 DEAL_II_ALWAYS_INLINE 3337...

Here is the whole backtrace: ``` #0 dealii::VectorizedArray::operator+= (vec=..., this=0x55555af7a340) at /home/bangerth/p/deal.II/1/install/include/deal.II/base/vectorization.h:3341 #1 dealii::internal::EvaluatorTensorProduct::apply (shapes=0x55555ac62580, in=0x55555af7a640, out=0x55555af7a340) at /home/bangerth/p/deal.II/1/install/include/deal.II/matrix_free/tensor_product_kernels.h:1876 #2 0x0000555558f6cb6c in dealii::internal::EvaluatorTensorProduct::gradients (this=0x7ffffffefef0, in=0x55555af7a640, out=0x55555af7a340) at /home/bangerth/p/deal.II/1/install/include/deal.II/matrix_free/tensor_product_kernels.h:1679 #3 0x0000555558f4d966...

Yes, it works now! Yay!

Do we know which deal.II commit caused this?

For reference, nothing in this function has changed this year, so it must be some upstream or downstream function.

/rebuild

@dravinsi When you write the documentation, please add these references to the file `doc/doxygen/references.bib` and then cite them via `@cite TAG`. This way, people can jump from the class documentation...

That ship has long sailed -- we're using `std::uint*_t` all over the place already :-) I'm in favor of `uint*_t` over `unsigned char` and similar because the former clearly indicates...

All of your patches work by overloading the `first_cell()`/`next_cell()` functions. I've long thought that these functions are no longer the way to do things -- it was what one would...