Comparing bdeb8b88b91...caddcd9b9dc · rust-lang/llvm (original) (raw)
This repository was archived by the owner on Feb 5, 2019. It is now read-only.
- 11 commits
- 14 files changed
- 6 contributors
Commits on Aug 30, 2018
- Configuration menu
Browse the repository at this point in the history - Configuration menu
Browse the repository at this point in the history - Disable checks for libatomic for now
For whatever reason this is failing the i686-freebsd builder in the Rust repo
as-of this red-hot moment. The build seems to work fine without it so let's just
remove it for now and pray there's a better fix later.
Although if you're reading this and know of a better fix, we'd love to remove
this!
Configuration menu
Browse the repository at this point in the history - Configuration menu
Browse the repository at this point in the history - Configuration menu
Browse the repository at this point in the history
Commits on Sep 6, 2018
- Configuration menu
Browse the repository at this point in the history - Configuration menu
Browse the repository at this point in the history
Commits on Sep 11, 2018
- [GlobalISel] Lower dbg.declare into indirect DBG_VALUE
Summary:
D31439 changed the semantics of dbg.declare to take the address of a
variable as the first argument, making it indirect. It specifically
updated FastISel for this change here:
https://reviews.llvm.org/D31439#change-WVArzi177jPl
GlobalISel needs to follow suit, or else it will be missing a level of
indirection in the generated debuginfo. This problem was seen in a Rust
debuginfo test on aarch64, since GlobalISel is used at -O0 for aarch64.
rust-lang/rust#49807
https://bugzilla.redhat.com/show_bug.cgi?id=1611597
https://bugzilla.redhat.com/show_bug.cgi?id=1625768
Reviewers: dblaikie, aprantl, t.p.northover, javed.absar, rnk
Reviewed By: rnk
Subscribers: #debug-info, rovka, kristof.beyls, JDevlieghere, llvm-commits, tstellar
Differential Revision: https://reviews.llvm.org/D51749
git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@341969 91177308-0d34-0410-b5e6-96231b3b80d8
Configuration menu
Browse the repository at this point in the history - Configuration menu
Browse the repository at this point in the history
Commits on Sep 15, 2018
- [PowerPC] Fix the calling convention for i1 arguments on PPC32
Summary:
Integer types smaller than i32 must be extended to i32 by default.
The feature "crbits" introduced at r202451 handles i1 as a special case,
but it did not extend properly.
The caller was, therefore, passing i1 stack arguments by writing 0/1 to
the first byte of the 4-byte stack object and callee was
reading the first byte for the value.
"crbits" is enabled if the optimization level is greater than 1,
which is very common in "release builds".
Such discrepancies with ABI specification also introduces
potential incompatibility with programs or libraries
built with other compilers e.g. GCC.
Fixes PR38661
Reviewers: hfinkel, cuviper
Subscribers: sylvestre.ledru, glaubitz, nagisa, nemanjai, kbarton, llvm-commits
Differential Revision: https://reviews.llvm.org/D51108
Configuration menu
Browse the repository at this point in the history - Configuration menu
Browse the repository at this point in the history