search for: cpprefer

Hello all, What Ruby reference is everybodies favorite? When I''ve been looking around for documentation I haven''t found any that quite compares to php.net''s and cppreference.com''s function references. I''ve been using the one found on rubycentral, but I think that it is missing quite a bit and doesn''t have very good examples. ri is fine, but can be a pain in the butt to navigate around. If there aren''t any really good ones out...

...ates <http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2013/n3651.pdf> Member initializers and aggregates (NSDMI) <http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2013/n3653.html> A bunch of new constexpr language and library features Various other language and library features See CppReference <https://en.cppreference.com/w/cpp/compiler_support> for details. Of these, I think polymorphic lambdas are the big feature. Of course, just like Almost Always Auto, we should use such things only where it makes sense. Toolchains We’re currently mandating: Clang 3.1 (released 2012/05)...

...docs/papers/2013/n3651.pdf> > - Member initializers and aggregates (NSDMI) > <http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2013/n3653.html> > - A bunch of new constexpr language and library features > - Various other language and library features > > See CppReference <https://en.cppreference.com/w/cpp/compiler_support> for > details. > > Of these, I think polymorphic lambdas are the big feature. Of course, just > like Almost Always Auto, we should use such things only where it makes > sense. > > > *Toolchains* > > We’re c...

...docs/papers/2013/n3651.pdf> > - Member initializers and aggregates (NSDMI) > <http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2013/n3653.html> > - A bunch of new constexpr language and library features > - Various other language and library features > > See CppReference <https://en.cppreference.com/w/cpp/compiler_support> for > details. > > Of these, I think polymorphic lambdas are the big feature. Of course, just > like Almost Always Auto, we should use such things only where it makes > sense. > > > *Toolchains* > > We’re c...

...get_sptr(); return 0; } This compiles fine, but throws a weak_ptr exception at runtime. I'm aware, that the implementation requires, that enable_shared_from_this needs to be publicly inherited, but as a first time user, I had to find this out the hard way, as documentations (I use, ie. cppreference.com) don't mention it, probably because it's not a requirement of the standard. On the other hand, if you compile the code with additional -Dprefix=boost (and needed boost stuff installed, of course), it gives a compiler error ( gcc: 'boost::enable_shared_from_this<foo>...

.../papers/2013/n3651.pdf> >>> Member initializers and aggregates (NSDMI) <http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2013/n3653.html> >>> A bunch of new constexpr language and library features >>> Various other language and library features >>> See CppReference <https://en.cppreference.com/w/cpp/compiler_support> for details. >>> >>> Of these, I think polymorphic lambdas are the big feature. Of course, just like Almost Always Auto, we should use such things only where it makes sense. >>> >>> >>> To...

On 08/12/2018 02:19 PM, Kim Gräsman wrote: > I still feel a little uncomfortable, because I think Jonathan makes an > excellent point -- if GCC thinks there's a strict-aliasing violation > (whether the standard agrees or not) and classifies this as undefined > behavior, we might invoke the optimizers wrath. The warning is a nice > hint that this could happen. Indeed. And

Dear all, I am using LLVM C++ API to generate some code. In particular, I am dealing with AVX2 SIMD API which uses __m256i. My function input types a set of vectors and return type is also a vector. /////////////////////////////////////////////////////////////////////////////////////////// arguments.push_back(VectorType::get(IntegerType::getIntNTy(TheContext, 64), 4));//int64*4 = __m256i

> } while (__c11_atomic_compare_exchange_weak( > addr, &oldval, newval, memory_order_seq_cst, memory_order_relaxed)); Actually, I think this condition is inverted. Should be "while (!_c11...". Sorry about that. Tim.

I am trying to cast a Value* irrespective of its underlying subclass to uint64 and pass it on to a method as an argument. if (StoreInst *store_inst = dyn_cast<StoreInst>(&I)) { Value* vo = store_inst->getValueOperand(); uint64 value = /* cast vo to unsigned int 64 bit */ func(value); } How can I force

...}; > ... > VecInt result = function(args0, ...); > > Btw.: Note that you may need to set target-feature attributes for your > function like so: [3] > > Hope it helps. > > Cheers, > Stefan > > [1] https://llvm.org/docs/LangRef.html#vector-type > [2] https://en.cppreference.com/w/cpp/container/vector > [3] https://en.cppreference.com/w/cpp/container/vector/data > [4] > https://github.com/weliveindetail/DecisionTreeCompiler/blob/master/compiler/DecisionTreeCompiler.cpp#L83 > > Am 20.07.18 um 02:02 schrieb Jia Yu via llvm-dev: > > Dear all, >...

Hi Kevin, On April 11, 2017 at 4:14:14 PM, Flamedoge (code.kchoi at gmail.com) wrote: > So only "non-freed" malloc pointers are No-Alias which makes it > flow-sensitive. There is no reason why malloc couldn't return previously > freed location. Yes. Talking to Nick Lewycky on IRC, I figured out a shorter way of saying what I wanted to say.  We know that programs like this

...ter literals > - Allow constant evaluation for all non-type template arguments > - Fold Expressions > - Unary fold expressions and empty parameter packs > - __has_include in preprocessor conditional > - Differing begin and end types in range-based for\ > > From: https://en.cppreference.com/w/cpp/compiler_support > <https://en.cppreference.com/w/cpp/compiler_support> > > The only thing that’s really nice are fold expressions, and I hope > they’re not buggy in GCC 6. > > Otherwise the list is missing a good amount for C++17 language > features, and br...

...51.pdf> >>>> Member initializers and aggregates (NSDMI) <http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2013/n3653.html> >>>> A bunch of new constexpr language and library features >>>> Various other language and library features >>>> See CppReference <https://en.cppreference.com/w/cpp/compiler_support> for details. >>>> >>>> Of these, I think polymorphic lambdas are the big feature. Of course, just like Almost Always Auto, we should use such things only where it makes sense. >>>> >>>>...

...s compiles fine, but throws a weak_ptr exception at runtime. >> I'm aware, that the implementation requires, that >> enable_shared_from_this needs to be publicly inherited, but as a first >> time user, I had to find this out the hard way, as documentations (I >> use, ie. cppreference.com) don't mention it, probably because it's not a >> requirement of the standard. > > It definitely is a requirement of the standard. The new wording we > added via http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2016/p0033r1.html#spec > says that the base's w...

Yes, this keyword is no longer valid starting from C++17:     https://en.cppreference.com/w/cpp/keyword/register I realize that the "why" probably doesn't help you move forth with your problem, so here are a couple suggestions how to get over it: * Build Boost in C++14 mode with -std=c++14 * Cut out "register" from the Boost source and rebuild *...

...and aggregates (NSDMI) >>>> <http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2013/n3653.html> >>>> - A bunch of new constexpr language and library features >>>> - Various other language and library features >>>> >>>> See CppReference <https://en.cppreference.com/w/cpp/compiler_support> for >>>> details. >>>> >>>> Of these, I think polymorphic lambdas are the big feature. Of course, >>>> just like Almost Always Auto, we should use such things only where it makes >>&...

Howdy all, I've been playing around with programs that use the C11 fenv.h. It seems that, currently, the LLVM compiler does not regard to the exception-flag side-effects of floating point operations? When run on my macbook, the example code on http://en.cppreference.com/w/c/numeric/fenv/FE_exceptions does not print all the expected exceptions. Other examples: void foo() { fesetround(FE_DOWNWARD); printf("foo downward: %f\n", rint(0.5)); fesetround(FE_UPWARD); printf("foo upward: %f\n", rint(0.5)); } If compiled w...

...e union member of > > the appropriate type? > > As it turns out, Union is not a union ¯\_(ツ)_/¯. (I thought it was, up > until this point.) > > It's a template producing a char array suitably aligned for any number > of mutually exclusive types, much like > https://en.cppreference.com/w/cpp/types/aligned_union. > > I can't tell if that makes the waters less dangerous, but there's an > invariant for this code that it only reinterpret_casts out Ts from the > char buffer that it has previously put in there using placement new. > As far as I can tell,...

...}; > ... > VecInt result = function(args0, ...); > > Btw.: Note that you may need to set target-feature attributes for your > function like so: [3] > > Hope it helps. > > Cheers, > Stefan > > [1] https://llvm.org/docs/LangRef.html#vector-type > [2] https://en.cppreference.com/w/cpp/container/vector > [3] https://en.cppreference.com/w/cpp/container/vector/data > [4] > https://github.com/weliveindetail/DecisionTreeCompiler/blob/master/compiler/DecisionTreeCompiler.cpp#L83 > > Am 20.07.18 um 02:02 schrieb Jia Yu via llvm-dev: > > Dear all, >...