https://github.com/rust-lang/rust http://git.dreamy.place/mirrors/rust/atom?h=0.11.0 2014-06-24T13:46:54+00:00 2014-06-24T13:46:54+00:00 bors bors@rust-lang.org 2014-06-24T13:46:54+00:00 urn:sha1:82ec1aef293ddc5c6373bd7f5ec323fafbdf7901 The aim of these changes is not working out a generic bi-endianness architectures support but to allow people develop for little endian MIPS machines (issue #7190). 2014-06-24T09:12:10+00:00 Pawel Olzacki p.olzacki2@samsung.com 2014-06-17T07:16:03+00:00 urn:sha1:34a384a128d9630679f9c90bb27eaa0822e5b798 2014-06-21T17:59:58+00:00 Björn Steinbrink bsteinbr@gmail.com 2014-06-17T19:51:24+00:00 urn:sha1:5e720aac4215dcd8ba1b0fd455a737d8798baea4 When calling a foreign function, some arguments and/or return value attributes are required to conform to the foreign ABI. Currently those attributes are only added to the declaration of foreign functions. With direct calls, this is no problem, because LLVM can see that those attributes apply to the call. But with an indirect call, LLVM cannot do that and the attribute is missing. To fix that, we have to add those attribute to the calls to foreign functions as well. This also allows to remove the special handling of the SRet attribute, which is ABI-dependent and will be set via the `attr` field of the return type's `ArgType`. 2014-06-13T07:18:12+00:00 Valerii Hiora valerii.hiora@gmail.com 2014-06-13T07:18:12+00:00 urn:sha1:ebc6474668ec60cc793af0f48143bf33d984deb4 2014-06-12T17:24:08+00:00 Valerii Hiora valerii.hiora@gmail.com 2014-05-05T07:08:34+00:00 urn:sha1:d730ae2fb0c455775fb1962454537c79e54f817e 2014-05-22T21:42:02+00:00 Patrick Walton pcwalton@mimiga.net 2014-05-20T00:06:54+00:00 urn:sha1:a9dd903d79b053eb85302572e53717ad865c813d It depends on `~str`. 2014-05-14T16:34:32+00:00 Daniel Micay danielmicay@gmail.com 2014-05-14T16:30:57+00:00 urn:sha1:779875591681eea522e780f44ef5e30c429f513f 2014-05-12T00:05:22+00:00 Daniel Micay danielmicay@gmail.com 2014-05-11T23:31:23+00:00 urn:sha1:f1735cefcfdee5260ea6961cf785f545a340ff85 This requires pointing it at the valgrind headers we carry in-tree. 2014-05-04T00:36:20+00:00 Alex Crichton alex@alexcrichton.com 2014-05-03T00:56:35+00:00 urn:sha1:9306e840f59ac22651c6177a89352bf5d607fcbd This primary fix brought on by this upgrade is the proper matching of the ``` and ~~~ doc blocks. This also moves hoedown to a git submodule rather than a bundled repository. Additionally, hoedown is stricter about code blocks, so this ended up fixing a lot of invalid code blocks (ending with " ```" instead of "```", or ending with "~~~~" instead of "~~~"). Closes #12776 2014-04-24T16:08:07+00:00 Alex Crichton alex@alexcrichton.com 2014-04-19T02:09:31+00:00 urn:sha1:58a51120a7916a7b8c64f6e0841ba536b02ba11c This update brings a few months of changes, but primarily a fix for the following situation. When creating a handle to stdin, libuv used to set the stdin handle to nonblocking mode. This would end up affect this stdin handle across all processes that shared it, which mean that stdin become nonblocking for everyone using the same stdin. On linux, this also affected *stdout* because stdin/stdout roughly point at the same thing. This problem became apparent when running the test suite manually on a local computer. The stdtest suite (running with libgreen) would set stdout to nonblocking mode (as described above), and then the next test suite would always fail for a printing failure (because stdout was returning EAGAIN). This has been fixed upstream, joyent/libuv@342e8c, and this update pulls in this fix. This also brings us in line with a recently upstreamed libuv patch. Closes #13336 Closes #13355