https://github.com/rust-lang/rust http://git.dreamy.place/mirrors/rust/atom?h=1.77.0 2023-12-23T21:05:28+00:00 2023-12-23T21:05:28+00:00 Nicholas Nethercote n.nethercote@gmail.com 2023-12-18T11:21:37+00:00 urn:sha1:99472c7049783605444ab888a97059d0cce93a12 Also add some `dcx` methods to types that wrap `TyCtxt`, for easier access. 2023-12-07T16:46:36+00:00 Ralf Jung post@ralfj.de 2023-11-25T17:41:53+00:00 urn:sha1:cb863033423d895c0530ab749e4a3bca494b5c27 2023-06-19T22:51:02+00:00 Antoni Boucher bouanto@zoho.com 2023-06-19T22:51:02+00:00 urn:sha1:4d96893d853a261e5d59c860108c3ddd3872c544 2023-06-01T14:45:18+00:00 Deadbeef ent3rm4n@gmail.com 2023-05-17T10:30:14+00:00 urn:sha1:4f83717cf768adb0b0dfe23b8eecf2b259eec354 2023-05-26T15:01:29+00:00 Oli Scherer git-spam-no-reply9815368754983@oli-obk.de 2023-05-19T15:48:43+00:00 urn:sha1:164d041e303e9c98daaf35301fa88ba6844277dd 2023-03-05T17:03:19+00:00 Antoni Boucher bouanto@zoho.com 2023-03-05T17:03:19+00:00 urn:sha1:6bb2af0e6d7e3a8cc176f2594079ef3c2946be14 2023-01-25T06:46:19+00:00 Erik Desjardins erikdesjardins@users.noreply.github.com 2023-01-25T06:46:19+00:00 urn:sha1:adc18904483fbd9df409291da4c4e299c8b6cb3e 2023-01-23T04:41:39+00:00 Erik Desjardins erikdesjardins@users.noreply.github.com 2023-01-23T04:03:58+00:00 urn:sha1:009192b01bd88a7bb6c1948d1f47dd598af0bfd9 ...and remove it from `PointeeInfo`, which isn't meant for this. There are still various places (marked with FIXMEs) that assume all pointers have the same size and alignment. Fixing this requires parsing non-default address spaces in the data layout string, which will be done in a followup. 2022-12-05T23:05:43+00:00 Peter Collingbourne pcc@google.com 2022-11-24T02:13:30+00:00 urn:sha1:5873ebeef3a4497c14b4199abba705fe7b530935 This ensures that the error is printed even for unused variables, as well as unifying the handling between the LLVM and GCC backends. This also fixes unusual behavior around exported Rust-defined variables with linkage attributes. With the previous behavior, it appears to be impossible to define such a variable such that it can actually be imported and used by another crate. This is because on the importing side, the variable is required to be a pointer, but on the exporting side, the type checker rejects static variables of pointer type because they do not implement `Sync`. Even if it were possible to import such a type, it appears that code generation on the importing side would add an unexpected additional level of pointer indirection, which would break type safety. This highlighted that the semantics of linkage on Rust-defined variables is different to linkage on foreign items. As such, we now model the difference with two different codegen attributes: linkage for Rust-defined variables, and import_linkage for foreign items. This change gives semantics to the test src/test/ui/linkage-attr/auxiliary/def_illtyped_external.rs which was previously expected to fail to compile. Therefore, convert it into a test that is expected to successfully compile. The update to the GCC backend is speculative and untested. 2022-11-06T13:17:10+00:00 Ralf Jung post@ralfj.de 2022-11-06T13:15:20+00:00 urn:sha1:eb4bdb00a4e1d881eaadc6254824bb0631950c5b