From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 19151 invoked by alias); 19 Jan 2015 20:13:25 -0000 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org Received: (qmail 19084 invoked by uid 48); 19 Jan 2015 20:13:21 -0000 From: "clyon at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug sanitizer/64435] [5 Regression] Bootstrap failure in libsanitizer on AArch64 with Linux kernel <= 3.15 Date: Mon, 19 Jan 2015 20:13:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: sanitizer X-Bugzilla-Version: 5.0 X-Bugzilla-Keywords: build X-Bugzilla-Severity: major X-Bugzilla-Who: clyon at gcc dot gnu.org X-Bugzilla-Status: NEW X-Bugzilla-Priority: P1 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: 5.0 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2015-01/txt/msg01891.txt.bz2 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64435 --- Comment #20 from clyon at gcc dot gnu.org --- (In reply to Jakub Jelinek from comment #14) > > https://github.com/torvalds/linux/blob/master/arch/arm64/include/asm/memory.h > https://github.com/torvalds/linux/blob/master/arch/arm64/Kconfig > reveals that aarch64 can be on Linux configured to support 39, 42 or 48 bits > virtual address space. The current libsanitizer/asan/ and > gcc/config/aarch64/aarch64.c (aarch64_asan_shadow_offset) seems to be okay > only for the 39 bits virtual address space, while Fedora/RHEL apparently use > 42 bits VA. Wonder if aarch64 couldn't use a layout closer to what x86_64 > uses for asan, with shadow offset low 0x7fff8000, which is flexible to > different sizes of the virtual address space. Thanks for pointing that, I wasn't aware of it when I worked on the initial port. My platform had 39 bits virtual address space, and I didn't notice there were other possibilities.