<feed xmlns='http://www.w3.org/2005/Atom'>
<title>bcm5719-llvm/libcxx/include/cstring, branch meklort-10.0.1</title>
<subtitle>Project Ortega BCM5719 LLVM</subtitle>
<id>https://git.raptorcs.com/git/bcm5719-llvm/atom?h=meklort-10.0.1</id>
<link rel='self' href='https://git.raptorcs.com/git/bcm5719-llvm/atom?h=meklort-10.0.1'/>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/bcm5719-llvm/'/>
<updated>2019-01-19T08:50:56+00:00</updated>
<entry>
<title>Update the file headers across all of the LLVM projects in the monorepo</title>
<updated>2019-01-19T08:50:56+00:00</updated>
<author>
<name>Chandler Carruth</name>
<email>chandlerc@gmail.com</email>
</author>
<published>2019-01-19T08:50:56+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/bcm5719-llvm/commit/?id=2946cd701067404b99c39fb29dc9c74bd7193eb3'/>
<id>urn:sha1:2946cd701067404b99c39fb29dc9c74bd7193eb3</id>
<content type='text'>
to reflect the new license.

We understand that people may be surprised that we're moving the header
entirely to discuss the new license. We checked this carefully with the
Foundation's lawyer and we believe this is the correct approach.

Essentially, all code in the project is now made available by the LLVM
project under our new license, so you will see that the license headers
include that license only. Some of our contributors have contributed
code under our old license, and accordingly, we have retained a copy of
our old license notice in the top-level files in each project and
repository.

llvm-svn: 351636
</content>
</entry>
<entry>
<title>Fix overload sets of strchr, strpbrk, strrchr, memchr and strstr from</title>
<updated>2016-02-10T00:59:02+00:00</updated>
<author>
<name>Richard Smith</name>
<email>richard-llvm@metafoo.co.uk</email>
</author>
<published>2016-02-10T00:59:02+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/bcm5719-llvm/commit/?id=5fd17ab1b093f6b59aabb27f6c2c2278e65c2707'/>
<id>urn:sha1:5fd17ab1b093f6b59aabb27f6c2c2278e65c2707</id>
<content type='text'>
&lt;string.h&gt; and wcschr, wcspbrk, wcsrchr, wmemchr, and wcsstr from &lt;wchar.h&gt; to
provide a const-correct overload set even when the underlying C library does
not.

This change adds a new macro, _LIBCPP_PREFERRED_OVERLOAD, which (if defined)
specifies that a given overload is a better match than an otherwise equally
good function declaration without the overload. This is implemented in modern
versions of Clang via __attribute__((enable_if)), and not elsewhere.

We use this new macro to define overloads in the global namespace for these
functions that displace the overloads provided by the C library, unless we
believe the C library is already providing the correct signatures.

llvm-svn: 260337
</content>
</entry>
<entry>
<title>Revert r249929 ("Split &lt;string.h&gt; out of &lt;cstring&gt;").</title>
<updated>2015-10-29T23:32:29+00:00</updated>
<author>
<name>Richard Smith</name>
<email>richard-llvm@metafoo.co.uk</email>
</author>
<published>2015-10-29T23:32:29+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/bcm5719-llvm/commit/?id=25cb32091cce2e6227e1f8812aea84b45000654e'/>
<id>urn:sha1:25cb32091cce2e6227e1f8812aea84b45000654e</id>
<content type='text'>
This change caused problems when building code like povray that:
a) uses 'using namespace std;'
b) is built on an environment where the C library provides the "wrong"
   (non-const-correct) interface for the str* functions
c) makes an unqualified call to one of those str* functions

A patch is out for review to add a facility to fix this (and to give the
correct signatures for these functions whenever possible, even when the C
library does not do so). This revert is expected to be temporary.

llvm-svn: 251665
</content>
</entry>
<entry>
<title>Split &lt;string.h&gt; out of &lt;cstring&gt;.</title>
<updated>2015-10-10T01:25:31+00:00</updated>
<author>
<name>Richard Smith</name>
<email>richard-llvm@metafoo.co.uk</email>
</author>
<published>2015-10-10T01:25:31+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/bcm5719-llvm/commit/?id=da231b4a3cd9481b756104dc20e11b44c02de0ed'/>
<id>urn:sha1:da231b4a3cd9481b756104dc20e11b44c02de0ed</id>
<content type='text'>
Also fix the overload set for the five functions whose signatures change in the
case where we can fix it. This is already covered by existing tests for the
affected systems.

llvm-svn: 249929
</content>
</entry>
<entry>
<title>Make support for thread-unsafe C functions optional.</title>
<updated>2015-06-24T08:44:38+00:00</updated>
<author>
<name>Ed Schouten</name>
<email>ed@nuxi.nl</email>
</author>
<published>2015-06-24T08:44:38+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/bcm5719-llvm/commit/?id=e0cf3b9a3ca8d80d313d1e2e5b8c70d73d10e933'/>
<id>urn:sha1:e0cf3b9a3ca8d80d313d1e2e5b8c70d73d10e933</id>
<content type='text'>
One of the aspects of CloudABI is that it aims to help you write code
that is thread-safe out of the box. This is very important if you want
to write libraries that are easy to reuse. For CloudABI we decided to
not provide the thread-unsafe functions. So far this is working out
pretty well, as thread-unsafety issues are detected really early on.

The following patch adds a knob to libc++,
_LIBCPP_HAS_NO_THREAD_UNSAFE_C_FUNCTIONS, that can be set to disable
thread-unsafe functions that can easily be avoided in practice. The
following functions are not thread-safe:

- &lt;clocale&gt;: locale handles should be preferred over setlocale().
- &lt;cstdlib&gt;: mbrlen(), mbrtowc() and wcrtomb() should be preferred over
  their non-restartable counterparts.
- &lt;ctime&gt;: asctime(), ctime(), gmtime() and localtime() are not
  thread-safe. The first two are also deprecated by POSIX.

Differential Revision:	http://reviews.llvm.org/D8703
Reviewed by:	marshall

llvm-svn: 240527
</content>
</entry>
<entry>
<title>Revert changes inadvertantly committed</title>
<updated>2015-06-02T22:26:29+00:00</updated>
<author>
<name>Marshall Clow</name>
<email>mclow.lists@gmail.com</email>
</author>
<published>2015-06-02T22:26:29+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/bcm5719-llvm/commit/?id=3ca2099fdf35351e77d9d3be1068d0d7ca8e62a1'/>
<id>urn:sha1:3ca2099fdf35351e77d9d3be1068d0d7ca8e62a1</id>
<content type='text'>
llvm-svn: 238880
</content>
</entry>
<entry>
<title>Move uncaught_exeption() definition inside the #ifdef block like uncaught_exceptions()</title>
<updated>2015-06-02T22:25:23+00:00</updated>
<author>
<name>Marshall Clow</name>
<email>mclow.lists@gmail.com</email>
</author>
<published>2015-06-02T22:25:23+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/bcm5719-llvm/commit/?id=ef96861df9a93c5554e4fb8478b7d9449d57c24f'/>
<id>urn:sha1:ef96861df9a93c5554e4fb8478b7d9449d57c24f</id>
<content type='text'>
llvm-svn: 238879
</content>
</entry>
<entry>
<title>Nico Rieck:  Currently _MSC_VER and _WIN32 are used to guard code which is</title>
<updated>2013-08-01T18:17:34+00:00</updated>
<author>
<name>Howard Hinnant</name>
<email>hhinnant@apple.com</email>
</author>
<published>2013-08-01T18:17:34+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/bcm5719-llvm/commit/?id=0be8f64c44d2fe87fdf8feda175dc39d38a83906'/>
<id>urn:sha1:0be8f64c44d2fe87fdf8feda175dc39d38a83906</id>
<content type='text'>
MSVC-specific, MSVCRT-specific, or Windows-specific. Because Clang can
also define _MSC_VER, and MSVCRT is not necessarily the only C runtime,
these macros should not be used interchangeably.

This patch divides all Windows-related bits into the aforementioned
categories. Two new macros are introduced:

- _LIBCPP_MSVC: Defined when compiling with MSVC. Detected using
  _MSC_VER, excluding Clang.
- _LIBCPP_MSVCRT: Defined when using the Microsoft CRT. This is the default
   when _WIN32 is defined.

This leaves _WIN32 for code using the Windows API.

This also corrects the spelling of _LIBCP_HAS_IS_BASE_OF to _LIBCPP_HAS_IS_BASE_OF.

Nico, please prepare a patch for CREDITS.TXT, thanks.

llvm-svn: 187593
</content>
</entry>
<entry>
<title>Change &lt;cwchar&gt; and &lt;cstring&gt; to look out for flags which may or may not be set by the C headers &lt;wchar.h&gt; and &lt;string.h&gt; indicating C support for the C++-altered wcschr, wcspbrk, wcsrchr, wcsstr, wmemchr, strchr, strpbrk, strrchr, memchr, and strstr.  This was already done in &lt;cstring&gt; for other platforms using other flags, so just had to add one more flag to the list there.</title>
<updated>2013-04-08T18:59:28+00:00</updated>
<author>
<name>Howard Hinnant</name>
<email>hhinnant@apple.com</email>
</author>
<published>2013-04-08T18:59:28+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/bcm5719-llvm/commit/?id=98381453c00de6773d01985062f3a2056044bfdc'/>
<id>urn:sha1:98381453c00de6773d01985062f3a2056044bfdc</id>
<content type='text'>
llvm-svn: 179041
</content>
</entry>
<entry>
<title>Solaris port.  Currently sees around 200 test failures, mostly related to</title>
<updated>2012-02-29T13:05:08+00:00</updated>
<author>
<name>David Chisnall</name>
<email>csdavec@swan.ac.uk</email>
</author>
<published>2012-02-29T13:05:08+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/bcm5719-llvm/commit/?id=14c25b80e9be5aab9b503a53f810c5bbffe4d632'/>
<id>urn:sha1:14c25b80e9be5aab9b503a53f810c5bbffe4d632</id>
<content type='text'>
Solaris not providing some of the locales that the test suite uses.

Note: This depends on an xlocale (partial) implementation for Solaris and a
couple of fixed standard headers.  These will be committed to a branch later
today.

llvm-svn: 151720
</content>
</entry>
</feed>
