public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "kcc at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug sanitizer/55975] asan does not work with 46 bit address space on PowerPC64
Date: Fri, 18 Jan 2013 15:34:00 -0000	[thread overview]
Message-ID: <bug-55975-4-AwAG5IHDDs@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-55975-4@http.gcc.gnu.org/bugzilla/>


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55975

--- Comment #21 from Kostya Serebryany <kcc at gcc dot gnu.org> 2013-01-18 15:33:33 UTC ---
While we are at it... 
It is possible to use zero shadow offset of powerpc somehow? 

on x86_64 linux, when I build the code with -fPIC -pie
the mapping looks like this: 

7fb6dda49000-7fb6ddbfe000 r-xp 00000000 fc:00 1208459                   
/lib/x86_64-linux-gnu/libc-2.15.so
...
7fff01eba000-7fff01edb000 rw-p 00000000 00:00 0                         
[stack]
7fff01f15000-7fff01f16000 r-xp 00000000 00:00 0                          [vdso]
ffffffffff600000-ffffffffff601000 r-xp 00000000 00:00 0                 
[vsyscall]

which allows us to occupy 16T of memory starting from zero for the shadow. 

On my power pc box, however, I get this mapping: 
36ec0000-36ed0000 r-xp 00000000 08:02 3213429                           
/tmp/a.out
36ed0000-36ee0000 rw-p 00000000 08:02 3213429                           
/tmp/a.out
fff7f360000-fff7f370000 rw-p 00000000 00:00 0 
...
fffe70d0000-fffe7100000 rw-p 00000000 00:00 0                           
[stack]

So, I can't use zero-based shadow. 

On x86_64 using zero-based shadow gives 5% speedup. It's worth trying on ppc as
well, I think.


  parent reply	other threads:[~2013-01-18 15:34 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-14 19:15 [Bug sanitizer/55975] New: FAIL: c-c++-common/asan/global-overflow-1.c -O0 output pattern test schwab@linux-m68k.org
2013-01-15  6:12 ` [Bug sanitizer/55975] " kcc at gcc dot gnu.org
2013-01-15 20:00 ` schwab@linux-m68k.org
2013-01-16 10:01 ` kcc at gcc dot gnu.org
2013-01-16 10:14 ` kcc at gcc dot gnu.org
2013-01-16 10:38 ` jakub at gcc dot gnu.org
2013-01-16 11:47 ` [Bug sanitizer/55975] asan does not work with 46 bit address space on PowerPC64 kcc at gcc dot gnu.org
2013-01-16 11:51 ` jakub at gcc dot gnu.org
2013-01-16 11:54 ` kcc at gcc dot gnu.org
2013-01-16 19:12 ` schwab@linux-m68k.org
2013-01-17  8:30 ` kcc at gcc dot gnu.org
2013-01-17 23:24 ` schwab@linux-m68k.org
2013-01-17 23:52 ` schwab@linux-m68k.org
2013-01-18  8:20 ` jakub at gcc dot gnu.org
2013-01-18  8:26 ` kcc at gcc dot gnu.org
2013-01-18 11:41 ` kcc at gcc dot gnu.org
2013-01-18 12:30 ` kcc at gcc dot gnu.org
2013-01-18 13:03 ` jakub at gcc dot gnu.org
2013-01-18 13:21 ` schwab@linux-m68k.org
2013-01-18 13:26 ` schwab@linux-m68k.org
2013-01-18 13:52 ` jakub at gcc dot gnu.org
2013-01-18 15:34 ` kcc at gcc dot gnu.org [this message]
2013-01-18 15:41 ` jakub at gcc dot gnu.org
2013-01-18 15:46 ` kcc at gcc dot gnu.org
2013-01-21  9:11 ` kcc at gcc dot gnu.org
2013-01-23 12:22 ` kcc at gcc dot gnu.org
2013-01-23 12:26 ` jakub at gcc dot gnu.org
2013-01-23 12:52 ` kcc at gcc dot gnu.org
2013-01-23 13:06 ` jakub at gcc dot gnu.org
2013-01-23 13:19 ` kcc at gcc dot gnu.org
2013-01-23 13:30 ` jakub at gcc dot gnu.org
2013-01-23 13:32 ` kcc at gcc dot gnu.org
2013-01-23 13:34 ` jakub at gcc dot gnu.org
2013-01-23 13:41 ` jakub at gcc dot gnu.org
2013-01-23 13:50 ` kcc at gcc dot gnu.org
2013-01-23 16:26 ` wschmidt at gcc dot gnu.org
2013-01-24  7:19 ` kcc at gcc dot gnu.org
2013-01-24 13:31 ` wschmidt at gcc dot gnu.org
2013-01-24 13:47 ` kcc at gcc dot gnu.org

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-55975-4-AwAG5IHDDs@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).