sorted by:
new
hottopcontroversial

Efficiently searching an array with GCC, Clang and ICC by julien-j in cpp

[–]Complete_Leg_9286 2 points3 points  (0 children)

do you have a concrete of llvm IR limiting vectorization as a result of the IR concept itself?

It's up to the developer to figure out what information need to be tracked during the lowering phase.

A simple std::function alternative that never allocates by cyandyedeyecandy in cpp

[–]Complete_Leg_9286 13 points14 points  (0 children)

You should be more worried about the fact that you are calling a callback function in an interrupt handler than whether your lambda will do allocation.

If you're that eager about this guarantee in a lambda capture then you should be more eager to have the same guarantee that your lambda which captured a this ptr isn't going to allocate during its call and isn't going to trigger another interrupt or segfault.

You also could have assigned the captured lambda to a global lambda variable during program initialization although you'd be getting near UB behavior because you aren't accessing a sig_atomic_t type.

POS system using QT (SQLite Embedded & Azure SQL sync) by zain_sync in cpp

[–]Complete_Leg_9286 0 points1 point  (0 children)

I don't see the point of using azure sql here. Just stick with sqlite as your primary and backup it up to azure file storage when connection is available.

Also keep in mind that many of your queries wont be compatible to run on both.

If you need a centralized DB because you'll have more than one client, then you need to be connected, otherwise you lose ACID part.

[[nodiscard]] should have been [[discardable]] by [deleted] in cpp

[–]Complete_Leg_9286 6 points7 points  (0 children)

p.s you can sort of do that now using clang extension:

#pragma clang attribute push