Bug#916818: rustc: Compiler regression results in generated code with unaligned access

2018-12-25 Thread John Paul Adrian Glaubitz
Hi! Additional note: Since this bug is considered rather serious, the fix for it has been nominated as a backport for the beta. Thus, the bug should be fixed in Rust 1.32 as well and it shouldn't be necessary to include the patch there. Adrian -- .''`. John Paul Adrian Glaubitz : :' :

Bug#916818: rustc: Compiler regression results in generated code with unaligned access

2018-12-21 Thread John Paul Adrian Glaubitz
On 12/21/18 12:55 PM, John Paul Adrian Glaubitz wrote: > On 12/21/18 10:19 AM, John Paul Adrian Glaubitz wrote: >> Attaching a better patch which can be applied unconditionally. > > Attaching a cleaned up patch after James' comments. And here with better formatting as well. Adrian -- .''`.

Bug#916818: rustc: Compiler regression results in generated code with unaligned access

2018-12-21 Thread John Paul Adrian Glaubitz
On 12/21/18 10:19 AM, John Paul Adrian Glaubitz wrote: > Attaching a better patch which can be applied unconditionally. Attaching a cleaned up patch after James' comments. Adrian -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer - glaub...@debian.org `. `' Freie Universitaet

Bug#916818: rustc: Compiler regression results in generated code with unaligned access

2018-12-21 Thread John Paul Adrian Glaubitz
Hi! On 12/20/18 9:40 AM, John Paul Adrian Glaubitz wrote: > If that's not feasible, I can also create a patch which changes the alignment > behavior specific to sparc64 in the code, so the patch can be applied to all > platforms. > > I'm still waiting for an opinion from upstream how this issue

Bug#916818: rustc: Compiler regression results in generated code with unaligned access

2018-12-20 Thread John Paul Adrian Glaubitz
Hi! On 12/20/18 9:25 AM, John Paul Adrian Glaubitz wrote: > The attached patch reverts the problematic upstream commit and fixes > the problem for me. > > Would it be possible to include it in the rustc source package and apply > it per platform, i.e. something like this in debian/rules: If

Bug#916818: rustc: Compiler regression results in generated code with unaligned access

2018-12-20 Thread John Paul Adrian Glaubitz
Control: tags -1 patch Hello! The attached patch reverts the problematic upstream commit and fixes the problem for me. Would it be possible to include it in the rustc source package and apply it per platform, i.e. something like this in debian/rules: ifeq ($(DEB_HOST_ARCH), sparc64)

Bug#916818: rustc: Compiler regression results in generated code with unaligned access

2018-12-18 Thread John Paul Adrian Glaubitz
Source: rustc Version: 1.31.0+dfsg1-2 Severity: normal Tags: upstream User: debian-sp...@lists.debian.org Usertags: sparc64 Hi! The build of rustc fails on sparc64 due to a compiler regression with multiple bus errors meaning that an unaligned access has occurred [1]. The upstream commit which