search for: rustc

...that, instead of shipping llvm-toolchain packages built with gcc, we are rebuilding everything a second time using the newly built clang. Now, when pushed to Debian, it caused some unexpected issues in particular with rust reported here: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=913271#35 rustc in Debian was building initially against libllvm built with gcc. It was working fine. The failure is now happening when the systems saw their libllvm upgraded to the stage2 bootstrap one. The beginning of the backtrace is the following (generating debug info): Thread 1 "rustc" received...

...tice currently expands to 0.11.4, - mockall depends on predicates-tree, - predicates-tree depends on predicates-core, - approx. two weeks ago, predicates-tree and predicates-core have seen *PATCHLEVEL* upgrades (1.0.7 -> 1.0.9, and 1.0.5 -> 1.0.6, respectively) that now require "rustc 1.64.0 or newer". RHEL-9.2 will eventually ship rustc 1.66, but RHEL-9.2 has not been released. The above rustc requirement bump breaks the nbdkit build on RHEL-9.1 -- which provides rustc 1.62. Restrict predicates-{tree,core} to {1.0.7,1.0.5}. (Side commentary: when such things can happen v...

On Wed, Nov 11, 2015 at 07:14:28PM -0800, Sean Silva via llvm-dev wrote: > Can you show a real benchmark that users have tried to write where the call > overhead of actually using an external function call is measurable? This is the wrong question. The correct question is: What useful benchmark cannot trivally factor out the overhead of the external function call. Yes, if you do

...fth Floor, Boston, MA 02110-1301 USA. >+ >+dnl Rust >+AC_ARG_ENABLE([rust], >+ AS_HELP_STRING([--disable-rust], [disable Rust language bindings]), >+ [], >+ [enable_rust=yes]) >+AS_IF([test "x$enable_rust" != "xno"],[ >+ AC_CHECK_PROG([RUSTC],[rustc],[rustc],[no]) >+ AC_CHECK_PROG([CARGO],[cargo],[cargo],[no]) >+],[ >+ RUSTC=no >+ CARGO=no >+ ]) >+AM_CONDITIONAL([HAVE_RUST],[test "x$RUSTC" != "xno" && test "x$CARGO" != "xno"]) So even if someone explicitly s...

...essage before on llvm.discourse.group or elsewhere -- I've been trying to get to the bottom of this for a while now and asked about this in a few different platforms before. I'm currently trying to debug a bug in a LLVM-generated Wasm code. The bug could be in the code that generates LLVM (rustc) or in the LLVM, I'm not sure yet. LLVM IR and Wasm can be seen in [1]. The problem is this line: (import "GOT.func" "_ZN4core3fmt3num3imp52_$LT$impl$u20$core..fmt..Display$u20$for$u20$i32$GT$3fmt17h9ba9fea9cadf7bd5E" (global (;3;) (mut i32))) The same symbol is alrea...

I have been working on adding proper tail (via `become`) to rustc. I was able to make them work (some parts of the type checker aren't implemented yet). However, I ran into an LLVM-related problem. LLVM claims to support proper tail calls when fastcc is used — but only on i386, x86-64 and PowerPC. Is this accurate? Will proper tail calls be supported on W...

...a dedicated > escape hatch to be used in place of the alternatives I’ve listed below. > Alternatives > > In no particular order: > > - Volatile stores > > Not ideal for benchmarking (isn’t guaranteed to cache), nonetheless I made > an attempt to measure the effects on Rustc’s set of benchmarks. However, I > found an issue with rustc which blocks attempts to measure the effect: > https://github.com/rust-lang/rust/issues/29663. > > - Inline asm which “uses” a pointer to the value > > Rust’s current solution. Needs stack space. > > - Inline...

I originally meant to post only the "vector.h" patch, but then (independently) nbdkit wouldn't build. Hence the other (rust plugin) patch. Laszlo Laszlo Ersek (2): common/utils: document empty_vector compound literal assignment plugins/rust: restrict predicates-{tree,core} to {1.0.7,1.0.5} common/utils/vector.h | 8 +++++++- plugins/rust/Cargo.toml | 2 ++ 2 files changed,

...on, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA. + +dnl Rust +AC_ARG_ENABLE([rust], + AS_HELP_STRING([--disable-rust], [disable Rust language bindings]), + [], + [enable_rust=yes]) +AS_IF([test "x$enable_rust" != "xno"],[ + AC_CHECK_PROG([RUSTC],[rustc],[rustc],[no]) + AC_CHECK_PROG([CARGO],[cargo],[cargo],[no]) +],[ + RUSTC=no + CARGO=no + ]) +AM_CONDITIONAL([HAVE_RUST],[test "x$RUSTC" != "xno" && test "x$CARGO" != "xno"]) \ No newline at end of file diff --git a/rust/Cargo.toml...

...having another pass ordering issue. Looking at the pass manager at https://github.com/llvm-mirror/llvm/blob/7034870f30320d6fbc74effff539d946018cd00a/lib/Transforms/IPO/PassManagerBuilder.cpp (the early SimplifyCfg now doesn't sink stores anymore! I can't wait until I can get to use that in rustc!) I find that the loop optimization group does not run after GVN: // Rotate Loop - disable header duplication at -Oz MPM.add(createLoopRotatePass(SizeLevel == 2 ? 0 : -1)); MPM.add(createLICMPass()); // Hoist loop invariants if (EnableSimpleLoopUnswitch) MPM.add(create...

...ing to eg. https://docs.microsoft.com/en-us/cpp/c-runtime-library/reference/finite-finitef?view=vs-2019 the header to include is float.h also the ymath.h file contains the comment /* ymath.h internal header */ so probably shall not be used. I do not know how compiler-rt works only tried to compile rustc that is using compiler-rt How shall I go forward with this problem? BR/Andreas Jonson -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20190404/a7ffce47/attachment-0001.html>

...One example of situation where this is useful is when building thread synchronization primitives, where avoiding false sharing can be a critical concern. Now, when it comes to implementation, I have this gut feeling that we probably do not need to hardcode every target's cache line size in rustc ourselves, because there is probably a way to get this information directly from the LLVM toolchain that we are using. Is my gut right on this one? And can you provide us with some details on how it should be done? Thanks in advance, Hadrien

...t;> So my questions to you are: >> >> - Has anybody here observed something similar while >> wokring on or with PGO? >> >> - Are there certain known characteristics of LLVM IR code >> that inhibit PGO's effectiveness and that IR produced by >> `rustc` might exhibit? >> >> - Does anybody know of a good source that describes how to >> effectively debug a problem like this? >> >> - Does anybody know of a small example program in C/C++ >> that is known to profit from PGO and that could be >> re-implem...

...wouldn't be surprised if there were some issues around it not passing necessary info to the gold plugin. Teresa On Mon, Sep 16, 2019 at 8:41 AM Michael Woerister <mwoerister at mozilla.com> wrote: > So one interesting observation has already come out of this: I > confirmed that `rustc` indeed uses `-ffunction-sections` and > `-fdata-sections` on all platforms except for macOS. When trying out > different linkers for a small test case [1], however, I found that > there were rather large differences in execution time: > > ld (no PGO) = 172 ms > ld (PGO) = 196 ms...

...linker. It should have -u__llvm_profile_runtime to force the profile runtime to be linked in. David On Mon, Sep 16, 2019 at 8:42 AM Michael Woerister via llvm-dev < llvm-dev at lists.llvm.org> wrote: > So one interesting observation has already come out of this: I > confirmed that `rustc` indeed uses `-ffunction-sections` and > `-fdata-sections` on all platforms except for macOS. When trying out > different linkers for a small test case [1], however, I found that > there were rather large differences in execution time: > > ld (no PGO) = 172 ms > ld (PGO) = 196 ms...

...performance improvement is still well below expectations, I think. So my questions to you are: - Has anybody here observed something similar while wokring on or with PGO? - Are there certain known characteristics of LLVM IR code that inhibit PGO's effectiveness and that IR produced by `rustc` might exhibit? - Does anybody know of a good source that describes how to effectively debug a problem like this? - Does anybody know of a small example program in C/C++ that is known to profit from PGO and that could be re-implemented in Rust for comparison? Thanks a lot for reading! Any...

...bit words in their DataRefImpls. This caused random failures when seeking around in object files. Let me know if any of this is questionable or you've suggestions on style, as I may submit subsequent bugs along these lines; we're using the LLVM object-file reading facilities in rustc, so will be fixing any bugs we encounter as we go. Thanks, -Graydon -------------- next part -------------- A non-text attachment was scrubbed... Name: pecoff.patch Type: text/x-patch Size: 4718 bytes Desc: not available URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20110331/be46...

...le runtime to be linked in. > > > > David > > > > On Mon, Sep 16, 2019 at 8:42 AM Michael Woerister via llvm-dev <llvm-dev at lists.llvm.org> wrote: > >> > >> So one interesting observation has already come out of this: I > >> confirmed that `rustc` indeed uses `-ffunction-sections` and > >> `-fdata-sections` on all platforms except for macOS. When trying out > >> different linkers for a small test case [1], however, I found that > >> there were rather large differences in execution time: > >> > >>...

...is when > building thread synchronization primitives, where avoiding false > sharing can be a critical concern. > > Now, when it comes to implementation, I have this gut feeling that > we probably do not need to hardcode every target's cache line size > in rustc ourselves, because there is probably a way to get this > information directly from the LLVM toolchain that we are using. Is > my gut right on this one? And can you provide us with some details > on how it should be done? > > Thanks in advance, > Hadrien >...

`cargo doc` will generate docs with long descriptions. I did not add the settings of outputting these docs to `/website`. This is because - by publishing this crate to crates.io, users can see the docs in `docs.rs` like `https://docs.rs/guestfs/<version>/guestfs/`. It is easy to hold multiple documents corresponding to each version. - the style of the documents generated by `cargo doc`