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/59018] [4.9 Regression] libsanitizer doesn't build for x32
Date: Wed, 06 Nov 2013 18:01:00 -0000	[thread overview]
Message-ID: <bug-59018-4-PBCtUBCQtq@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-59018-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #5 from Kostya Serebryany <kcc at gcc dot gnu.org> ---

> Can you try
> 
>   register void *r8 __asm__ ("r8") = newtls;
>   register int *r10 __asm__ ("r10") = child_tidptr;
Yep, works! 

> But you need to enable x32 first on your OS, which requires
> 
> 1. x32 enabled kernel, Linux kernel >= 3.4.0.
> 2. x32 glibc.

This does not match my system. :( 
Do you have a VM image (e.g. for VMWare player) with such a system? 

> 
> > 
> > 2. Is there any chance to test x32 off the clang tree, so that we keep the
> > upstream tree x32-clean all the time?
> 
> There was x32 port of llvm/clang last year.  But only parts
> of the x32 patches have been merged with llvm.

Do you need help with this? 
I'll be on the LLVM dev meeting today and tomorrow, may at least ask around.


  parent reply	other threads:[~2013-11-06 18:01 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-06 10:26 [Bug sanitizer/59018] New: " hjl.tools at gmail dot com
2013-11-06 10:27 ` [Bug sanitizer/59018] " hjl.tools at gmail dot com
2013-11-06 17:48 ` jakub at gcc dot gnu.org
2013-11-06 17:58 ` kcc at gcc dot gnu.org
2013-11-06 18:01 ` kcc at gcc dot gnu.org [this message]
2013-11-06 18:04 ` hjl.tools at gmail dot com
2013-11-06 18:07 ` hjl.tools at gmail dot com
2013-11-06 18:15 ` kcc at gcc dot gnu.org
2013-11-06 21:51 ` hjl at gcc dot gnu.org
2013-11-06 21:52 ` hjl at gcc dot gnu.org
2013-11-06 21:53 ` hjl at gcc dot gnu.org
2013-11-06 21:54 ` hjl at gcc dot gnu.org
2013-11-06 23:54 ` hjl.tools at gmail dot com

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-59018-4-PBCtUBCQtq@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).