search for: 1z

The upcoming C++1z (probably C++17) standard will not contain several things - most notably auto_ptr. Soon, libc++ will not be providing auto_ptr by default when building in C++1z mode. You'll be able to get it back with a "-D_LIBCPP_ENABLE_CXX17_REMOVED_AUTO_PTR" on your command line, or "#define...

It is my pleasure to announce that LLVM 3.6 is now available! Get it here: http://llvm.org/releases/ This release contains the work of the LLVM community over the past six months: many many bug fixes, optimization improvements, support for more proposed C++1z features in Clang, better native Windows compatibility, embedding LLVM IR in native object files, Go bindings, and more. For details, see the release notes: http://llvm.org/releases/3.6.0/docs/ReleaseNotes.html http://llvm.org/releases/3.6.0/tools/clang/docs/ReleaseNotes.html Many thanks to everyo...

It is my pleasure to announce that LLVM 3.6 is now available! Get it here: http://llvm.org/releases/ This release contains the work of the LLVM community over the past six months: many many bug fixes, optimization improvements, support for more proposed C++1z features in Clang, better native Windows compatibility, embedding LLVM IR in native object files, Go bindings, and more. For details, see the release notes: http://llvm.org/releases/3.6.0/docs/ReleaseNotes.html http://llvm.org/releases/3.6.0/tools/clang/docs/ReleaseNotes.html Many thanks to everyo...

...all of C++20, and it builds with only C++11, so we > shouldn't have to worry too much about the problem of needing to "daisy > chain" compilers to finally get the latest version of LLVM building. "GCC > 4.8 -> Clang 6 - > Clang ToT" should hold up through C++1z. I don't understand how this argument holds. If we change the minimum c++ standard we build with every time one comes out, we'll definitely have a long daisy chain of compilers that need to be built to start working on LLVM at all. > * While we obviously can't be tied to the versio...

...ce > >Best regards, >-- >Charles Polisher Charles As the original note pointed out, /var/log/mysqld.log does not exist, as shown by these two commands: [root at goat ~]# ls -1F /var/log/mysqld.log ls: cannot access /var/log/mysqld.log: No such file or directory [root at goat ~]# ls -1Z /var/log/mysqld.log ls: cannot access /var/log/mysqld.log: No such file or directory [root at goat ~]# HOWEVER, /var/log/mariadb/mariadb.log does exist and is empty [root at goat ~]# ls -l /var/log/mariadb/* -rw-r----- 1 mysql mysql 0 Sep 23 10:08 /var/log/mariadb/mariadb.log David PS: I forgot...

...about deviances and degrees of freedom. I can see how to determine whether each term is predictive - 1-pchisq(deviance, df) - but how can I tell whether the relationship between 'z' and 'Y' is the same or different at each level of 'x'? ie, is the change in logodds of Y for 1z significantly different from the change in logodds of Y for 0z? I have had no luck tracking this down using Google. Many thanks to those who take up my question! *Peter M Milne* *Dept of Linguistics**, University of Ottawa* Tel: (613) 562-5800 x1125 | Fax: (613) 562-5141 aix2.uottawa.ca/~pmiln099...

Dear testers, 8.0.0-rc2 has been tagged from the release_80 branch at r353413. Please run the test script, share your results, and upload binaries. I'll get the source tarballs and docs published as soon as possible, and binaries as they become available. Thanks, Hans

...21663). * Support for `__has_cpp_attribute` is now present. [r221991](http://reviews.llvm.org/rL221991). ## Other project commits * Breakpoint stop/resume has been implemented on Windows for LLDB. [r221642](http://reviews.llvm.org/rL221642). * The [libcxx status page](http://libcxx.llvm.org/cxx1z_status.html) has been updated with the current state of C++1z support. [r221601](http://reviews.llvm.org/rL221601)).

...generation, support for iOS, and significantly faster compile times at -O0. Clang makes a considerable jump forward as well, including new warnings and better support for new standards: in addition to full support for the recently completed C++’14 standard, it includes initial support for "C++1z” features. Additionally, it now supports generating “remarks” to indicate when optimizations like vectorization and inlining occur, allowing you to tune your programs more effectively. On Windows, Clang now uses the updated MingW ABI for compatibility with GCC 4.7 and later. Clang has also seen...

...0806060748w505351bcx74b31b10f81318e@mail.gmail.com> <E1K4dK4-0000Ik-6x@intern.SerNet.DE> <cb44e8370806061342v327eba2bod4b85ec5d76e24c@mail.gmail.com> <E1K4rZB-0000VE-NC@intern.SerNet.DE> <cb44e8370806062319u61d5c932g64a8f788f9f37a66@mail.gmail.com> <E1K4s0e-00071j-1Z@intern.SerNet.DE> <cb44e8370807201927h4cb7b85bg7da4af87004455a7@mail.gmail.com> Message-ID: <E1KKo6J-009MMD-77@intern.SerNet.DE> On Mon, Jul 21, 2008 at 12:27:42PM +1000, Jean-Yves Avenard wrote: > Arggg... > > 2008/6/7 Volker Lendecke <Volker.Lendecke@sernet.de>: &...

...all of C++20, and it builds with only C++11, so we > shouldn't have to worry too much about the problem of needing to "daisy > chain" compilers to finally get the latest version of LLVM building. "GCC > 4.8 -> Clang 6 - > Clang ToT" should hold up through C++1z. > > * While we obviously can't be tied to the versioning of every single distro > out there, some are "bigger" than others. Which are big enough that > warrant serious consideration? The ones I found are (and I did my best to > aggregate all this, but please correct...

...$BO=L?-J#/1L._19&0)N*19XG_=ZO_=\W_=^__> M'_B"/_A>4>5>SAS9F^6$O_@,<1$980,TP!(G$1(C 1(F<1(PH!,:T1([ 0,T M$ ,P,0,P,!(Q$/FE[Q&,G_H^D2='D10GC/<*=V1A<14RD!4?L16JG_NZW_=D M at 8-KX8^086:=>'H at H 0N, 1A0%=WR09 ( ;[Q' \Y@)U\$^ESQM:N!HWP2#5 MW>57?FW1Z@;<(XA+8FL63.3L"@8XJ&7)+QSUSIPXZ(+U*@)9VJKW&J,I:O[0 M"5<@\-X,6^0E</!#*^IU*83Q=]2=BFA35T9>#)ON0+ML _^;6)O+R94 *96\ MK at .O"#:U)0^(O=2U&ZJ/&>@W/6)8,#PH158J1/S2+^#JULB)!NA2-B#P4@$J M (P$*=X"<[[>E5I4( &BKU'58U(EOH*7;.G0(R_3O0& H_L25^...

...elease_80 @svn). looks > similar to https://bugs.llvm.org/show_bug.cgi?id=40559 > > > (...)/clang++ -fPIC -target x86_64-linux-gnu --sysroot=(...) -march=x86-64 > -fuse-ld=lld -D_LIBCPP_ENABLE_CXX17_REMOVED_AUTO_PTR > -D_LIBCPP_ENABLE_CXX17_REMOVED_BINDERS -stdlib=libc++ -std=gnu++1z > -flto=thin > (...) > In file included from > (...)/sysroot-x86_64-linux-gnu/usr/include/c++/v1/string:500: > In file included from > (...)/sysroot-x86_64-linux-gnu/usr/include/c++/v1/string_view:176: > In file included from > (...)/sysroot-x86_64-linux-gnu/usr/include/c++/...

...ly C++11, so we >> > shouldn't have to worry too much about the problem of needing to "daisy >> > chain" compilers to finally get the latest version of LLVM building. >> "GCC >> > 4.8 -> Clang 6 - > Clang ToT" should hold up through C++1z. >> > >> > * While we obviously can't be tied to the versioning of every single >> distro >> > out there, some are "bigger" than others. Which are big enough that >> > warrant serious consideration? The ones I found are (and I did my best &g...

On Oct 21, 2007, at 6:23 PM, BGB wrote: > ok, just in my case, I guess I am a little fussy/weird, wanting > efficient dot and cross products (if at all possible, though these > operations at present don't exist natively within SSE...), among > many other operations (length, lerp, renormalization, ..). > > then again, probably a fairly smart compiler could still get

...t builds with only C++11, so we > > shouldn't have to worry too much about the problem of needing to "daisy > > chain" compilers to finally get the latest version of LLVM building. > "GCC > > 4.8 -> Clang 6 - > Clang ToT" should hold up through C++1z. > > > > * While we obviously can't be tied to the versioning of every single > distro > > out there, some are "bigger" than others. Which are big enough that > > warrant serious consideration? The ones I found are (and I did my best > to > > aggr...

...builds with only C++11, so we > > shouldn't have to worry too much about the problem of needing to "daisy > > chain" compilers to finally get the latest version of LLVM building. >  "GCC > > 4.8 -> Clang 6 - > Clang ToT" should hold up through C++1z. > > > > * While we obviously can't be tied to the versioning of every single > distro > > out there, some are "bigger" than others.  Which are big enough that > > warrant serious consideration?  The ones I found are (and I did my > best to > > ag...

...t builds with only C++11, so we > > shouldn't have to worry too much about the problem of needing to "daisy > > chain" compilers to finally get the latest version of LLVM building. > "GCC > > 4.8 -> Clang 6 - > Clang ToT" should hold up through C++1z. > > > > * While we obviously can't be tied to the versioning of every single > distro > > out there, some are "bigger" than others. Which are big enough that > > warrant serious consideration? The ones I found are (and I did my best > to > > aggr...

Reminder: The plan is to create the 3.6 branch next week, on 14 January. Please help get the release notes and other documents updated. For example, both the LLVM [1] and Clang [2] release notes look pretty empty. Also, if you'd like to volunteer to be a release tester, please let me know. Cheers, Hans 1. http://llvm.org/docs/ReleaseNotes.html 2.

...and it builds with only C++11, so we > > shouldn't have to worry too much about the problem of needing to "daisy > > chain" compilers to finally get the latest version of LLVM building. "GCC > > 4.8 -> Clang 6 - > Clang ToT" should hold up through C++1z. > > > > * While we obviously can't be tied to the versioning of every single distro > > out there, some are "bigger" than others. Which are big enough that > > warrant serious consideration? The ones I found are (and I did my best to > > aggregate all...