search for: x32

X32 support patch for compiler-rt. Applies against current trunk. --- projects/compiler-rt/make/platform/clang_linux.mk~ 2013-08-21 06:27:38.000000000 +0000 +++ projects/compiler-rt/make/platform/clang_linux.mk 2013-08-21 11:16:55.891621025 +0000 @@ -41,7 +41,18 @@ SupportedArches += x86_64 e...

Hi Steven, This looks interesting and raises a number of questions :) 1) Does applying this patch actually bring working sanitizers to x32 platform? That is, after you build the clang, does "clang -fsanitize=whatever foo.c" compile/link/run with expected results? I doubt that, as there is some platform-specific code in all the sanitizers, and many of them heavily depend on the address space layout. Porting TSan and MSan to 3...

If you are interesting to play around X32, you may refer to http://sourceware.org/glibc/wiki/x32 to bootstrap a local environment on Linux. Yours - Michael -----Original Message----- From: cfe-commits-bounces at cs.uiuc.edu [mailto:cfe-commits-bounces at cs.uiuc.edu] On Behalf Of Liao, Michael Sent: Monday, June 04, 2012 5:09 PM To: llvm...

Hi Folks, Anyone got chance to review the patch adding X32 psABI support? Yours - Michael -----Original Message----- From: llvm-commits-bounces at cs.uiuc.edu [mailto:llvm-commits-bounces at cs.uiuc.edu] On Behalf Of Liao, Michael Sent: Tuesday, June 05, 2012 11:18 AM To: llvm-commits at cs.uiuc.edu; cfe-commits at cs.uiuc.edu; llvmdev at cs.uiuc.edu; cf...

Hi all, We (Intel) would like to revive this thread on X32 ABI support upstreaming. X32 ABI homepage is here: https://sites.google.com/site/x32abi/ Currently x32 support is available in kernel/glibc/gcc/binutils and one can install for example Ubuntu 14 with extra x32 lib packages (apt-get install libc6-dev-x32) to evaluate x32-target code generated by GC...

Clang patch for X32 support. Applies against current trunk. --- ./tools/clang/include/clang/Driver/Options.td.orig 2013-05-16 21:51:51.286129820 +0000 +++ ./tools/clang/include/clang/Driver/Options.td 2013-05-16 21:53:24.875004239 +0000 @@ -841,6 +841,7 @@ HelpText<"Enable hexagon-qdsp6 backward compatibi...

This is a klibc port to x32 architecture. I tried to reuse as many existing files as possible, hence, a script making symlinks to x86-64 files. I was running this on Debian for about six months and hopefully, found any close to surface bugs. Of course, there are plenty left. Please help with testing. To build you need to run:...

Hi, I'm working on bringing up complete coverage for a Gentoo x32 "desktop" system. I've been cooking up quite a few patches for various packages to push upstream, but right now, the biggest blocker is the lack of support for building with/codegen targeting x32 in llvm/clang. Since the x32 patches were sent last year, I see support code has landed...

...at 11:27 +0400, Alexey Samsonov wrote: > > > > > Hi Steven, > > > > > > > > > > This looks interesting and raises a number of questions :) > > > > > > > > > > 1) Does applying this patch actually bring working sanitizers to x32 > > > > > platform? > > > > > That is, after you build the clang, does "clang -fsanitize=whatever > > > > foo.c" > > > > > compile/link/run with expected results? > > > > > I doubt that, as there is some platform-spec...

...suggestions for improvement. The next step: The second portion that we would like to upstream is in preparation for our x86-64 Native Client changes. In particular, our ABI is dependent on the existence of an ILP32 ABI on x86-64. The conventions we rely on are the same as those developed for the x32 effort, and we propose that the community begin reviewing changes to implement the x32 ABI. It should also be noted that the x32 ABI is already supported by binutils, gcc, and glibc, and that the Native Client team hopes to host its changes there on top of x32 as well. Our proposal is that the co...

...rg.uk>wrote: > > > On Thu, 2013-08-22 at 11:27 +0400, Alexey Samsonov wrote: > > > Hi Steven, > > > > > > This looks interesting and raises a number of questions :) > > > > > > 1) Does applying this patch actually bring working sanitizers to x32 > > > platform? > > > That is, after you build the clang, does "clang -fsanitize=whatever > > foo.c" > > > compile/link/run with expected results? > > > I doubt that, as there is some platform-specific code in all the > > > sanitizers, an...

On Thu, 2013-08-22 at 15:22 +0100, Steven Newbury wrote: > This patch is still not creating elf32_x86_64 objects. No idea > why. :( It does however, fix elf_x86_64 (-m64) code generation on x32 > hosts which is nice. :) I know why. I had assumed Michael Liao (the original patch author) had submitted all the _LLVM_ x32 support as separate patches, and it was just the tests/Clang/compiler-rt support that was missing. It seems not so. Those specific patches he did submit got commited,...

...; > On Thu, 2013-08-22 at 11:27 +0400, Alexey Samsonov wrote: > > > > Hi Steven, > > > > > > > > This looks interesting and raises a number of questions :) > > > > > > > > 1) Does applying this patch actually bring working sanitizers to x32 > > > > platform? > > > > That is, after you build the clang, does "clang -fsanitize=whatever > > > foo.c" > > > > compile/link/run with expected results? > > > > I doubt that, as there is some platform-specific code in all the >...

Hi, There's several, to my eyes, somewhat related looking bugs: Bug 36743 - Cannot select: X86ISD::CALL ICE with -mx32 -O2 -fno-plt https://bugs.llvm.org/show_bug.cgi?id=36743 Bug 34268 - JITting of x32 code on x64 fails with crash or instruction selection error. https://bugs.llvm.org/show_bug.cgi?id=34268 There's unfortunately been no investigation. I'm asking because I hit something eerily looking like...

...> The next step: > The second portion that we would like to upstream is in preparation > for our x86-64 Native Client changes. In particular, our ABI is > dependent on the existence of an ILP32 ABI on x86-64. The > conventions we rely on are the same as those developed for the > x32 effort, and we propose that the community begin reviewing > changes to implement the x32 ABI. It should also be noted that the > x32 ABI is already supported by binutils, gcc, and glibc, and that > the Native Client team hopes to host its changes there on top of > x32 as well. > &gt...

...ven Newbury <steve at snewbury.org.uk>wrote: > On Thu, 2013-08-22 at 11:27 +0400, Alexey Samsonov wrote: > > Hi Steven, > > > > This looks interesting and raises a number of questions :) > > > > 1) Does applying this patch actually bring working sanitizers to x32 > > platform? > > That is, after you build the clang, does "clang -fsanitize=whatever > foo.c" > > compile/link/run with expected results? > > I doubt that, as there is some platform-specific code in all the > > sanitizers, and many of them heavily depend...

On Thu, 2013-08-22 at 11:27 +0400, Alexey Samsonov wrote: > Hi Steven, > > This looks interesting and raises a number of questions :) > > 1) Does applying this patch actually bring working sanitizers to x32 > platform? > That is, after you build the clang, does "clang -fsanitize=whatever foo.c" > compile/link/run with expected results? > I doubt that, as there is some platform-specific code in all the > sanitizers, and many of them heavily depend > on the address space layo...

Rafa?l Carr? wrote: > That would need a special case for Linux x32 which is x86_64 with 32 > bits pointers It won't be wrong for x32, just sub-optimal. Please feel free to suggest a way to detect x32. Erik -- ---------------------------------------------------------------------- Erik de Castro Lopo http://www.mega-nerd.com/

Hi Pavel, We (the Native Client team) are also interested in helping you get these reviewed and in, especially the x86 backend stuff. Native Client's x86-64 ABI is similar to x32 so we could probably share a good portion of the code if it's structured the right way. -Derek On 1404316081542, Dmitri Gribenko <gribozavr at gmail.com> wrote: > On Wed, Jul 2, 2014 at 3:59 PM, Pavel Chupin <pavel.v.chupin at gmail.com> > wrote: > > Any suggestions a...

On Thu, Aug 22, 2013 at 7:56 AM, Steven Newbury <steve at snewbury.org.uk> wrote: > If I'm going to submit the Clang patch, how should it be submitted? One > patch with what's required to get x32 host to work, then another > enabling x32 code generation once the required changes to llvm are > merged? Would that be sufficient? Sounds good to me. Dmitri -- main(i,j){for(i=2;;i++){for(j=2;j<i;j++){if(!(i%j)){j=0;break;}}if (j){printf("%d\n",i);}}} /*Dmitri Gribenko <...