similar to: [LLVMdev] Does compiling LLVM on PowerPC64 always requires -mminimal-toc?

Kai, As I recall, this is required for gcc (but maybe not if you have a very recent version), and is not required when compiling with clang. -Hal ----- Original Message ----- > Hi! > > I always have to specify the flag -mminimize-toc when compiling on a > PowerPC64 architecture (Linux, AIX). Is this the preferred way or are > there other/better solutions? > > If this

On Tue, 01 May 2012 15:10:56 -0500 Peter Bergner <bergner at vnet.ibm.com> wrote: > On Sat, 2012-04-28 at 15:51 -0500, Hal Finkel wrote: > > > > - There is no support for generating position-independent code > > > > on PPC32. (PIC on PPC64 now works well). Nevertheless, I have > > > > sometimes run into linking errors when compiling shared > >

This fixes a segmentation fault in the system call's error handling path with dynamically-linked binaries on PowerPC64 little endian. The system call stub wasn't loading up r2 with the appropriate TOC value in its global entry point. The r2 setup code comes from the FUNC_START macro in gcc [1] and an equivalent one can also be found in the LOCALENTRY macro in glibc [2]. On the ELFv2 ABI

On Tue, 2012-05-01 at 16:06 -0500, Hal Finkel wrote: > LLVM/clang now will build in the normal way (./configure; make install) > on PPC (you'll need at least the 3.1 release candidate (or trunk)). I > generally build on my PPC64 hosts with: > make ENABLE_OPTIMIZED=1 OPTIMIZE_OPTION=-O2 EXTRA_OPTIONS=-mminimal-toc Ok, it built fine, but what is the llvm equivalent of gcc's -m32

On Tue, 01 May 2012 17:23:07 -0500 Peter Bergner <bergner at vnet.ibm.com> wrote: > On Tue, 2012-05-01 at 16:06 -0500, Hal Finkel wrote: > > LLVM/clang now will build in the normal way (./configure; make > > install) on PPC (you'll need at least the 3.1 release candidate (or > > trunk)). I generally build on my PPC64 hosts with: > > make ENABLE_OPTIMIZED=1

On Sat, 2012-04-28 at 15:51 -0500, Hal Finkel wrote: > > > - There is no support for generating position-independent code on > > > PPC32. (PIC on PPC64 now works well). Nevertheless, I have > > > sometimes run into linking errors when compiling shared libraries > > > with C++ on PPC64. PPC64 is PIC by nature. As for the linking issue, possibly you blew the

I was going through the config.log after installing R successfully on a Linux ppc64 machine. However, I could not install the MCMCpack and looked at the config.log file for gcc and g++ errors.I found some of them and have pasted them below. Please let me know if they can affect the installation of other packages on R. ------------------ configure:7479: checking whether we are using the GNU

Hi! I am still working on the Win64 EH code and now have a pretty usable result. (The MC part is already posted to llvm-commits, the other part follows soon. If you are curious the whole patch is here: http://www.redstar.de/ldc/win64eh_all_20130524.diff.) However, in one case I have a problem with LLVM being too smart. Consider the following D code: void doIt() { printf("doIt:

On Sat, 28 Apr 2012 13:55:13 -0500 Hal Finkel <hfinkel at anl.gov> wrote: > On Sat, 28 Apr 2012 13:46:02 -0500 > Hal Finkel <hfinkel at anl.gov> wrote: > > > On Sat, 28 Apr 2012 11:19:13 -0500 > > Peter Bergner <bergner at vnet.ibm.com> wrote: > > > > > On Fri, 2012-04-27 at 20:30 -0500, Hal Finkel wrote: > > > > Thanks! Do you

Hi, On 15.04.2014 23:44, Vadim Chugunov wrote: > Hi, > I am curious - how does clang deal with epilogue-less functions that > result from _Raise_Exception being marked 'noreturn'? > I've also been playing with Kai's patch, and discovered that this tends > to greatly confuse Windows stack unwinder in cases when noreturn call is > at the end of a function, so

Hi! Sorry for delay, just returned from vacation. On 12/11/15 23:44, Kostya Serebryany via llvm-dev wrote: > +Maxim and Yuri, as I think this is their code. > > On Thu, Nov 12, 2015 at 3:02 AM, Jay Foad <jay.foad at gmail.com > <mailto:jay.foad at gmail.com>> wrote: > > (Resending with the correct mailing list address.) > > Hi, > > Currently

(Resending with the correct mailing list address.) Hi, Currently test/asan/TestCases/alloca_vla_interact.cc is XFAILed for powerpc64. I've had a look at why it doesn't work. I think the only problem is in the call to __asan_allocas_unpoison that is inserted at the end of the "for" loop (just before a stackrestore instruction). The call function is created something like this

On 11 December 2013 05:41, Kai Nacke <kai.nacke at redstar.de> wrote: > Maybe we should also change the stack probing code. I think ___chkstk_ms is > used since gcc 4.6. It simplifies the prologue generation code a bit. I just checked gcc 4.6 and looks like you are right, it uses ___chkstk_ms. LGTM. We should probably commit this first, since it is common for gcc 4.6 and newer.

Jay, do you have a PowerPC64 target? If so, could you please check attached patch on PPC box? This is a draft patch, but it would be nice to make sure that we are moving to right direction here. Thanks, -Maxim On 18/11/15 00:12, Jay Foad wrote: >>> Currently test/asan/TestCases/alloca_vla_interact.cc is XFAILed for >>> powerpc64. I've had a look at why it

Hola. Pare que RStudio y el paquete markdown no nos terminamos de entender. - Creo un fichero Rmd, con el botón: "Kntr to Html" (ctr+Shift+Y), se pre-visualiza genial: formulas (, highlight_code,...)... todo bien. Pero quiero ponerle un TOC tb, así que como en su día me comento Jose Luis Cañadas en este foro, hago un desde el fichero md que crea la previsualización ("Kntr to

Hi all! On x86_64, segment prefix fs: is in address space 257 and gs: in address space 256. (BTW: are there constants for these magic values?) How can I use this in IR? I want to express this assembler code in IR: mov RAX, 8; mov RAX, GS:[RAX]; ret; I tried the following: define i64 @getStackBottom(i64 %addr) { entry: %ptr = inttoptr

Hi there! The attached patch fixes a few places where 32bit register classes or instructions are used on PowerPC64. This lets me compile a working "vim" at -O0 on PowerPC64/FreeBSD. Previously it would crash the compiler with llvm_unreachable("Impossible reg-to-reg copy"); As it was mixing 64 bit registers with 32bit ones. Vim compiled with -O2 still crashes. OK

In LowerGET_DYNAMIC_AREA_OFFSET() you're calling MFI->getMaxCallFrameSize(), but it looks like that doesn't return useful information until after the PrologEpilogInserter's PEI::calculateCallsInformation() has run. So maybe the lowering has to be done as part of frame index elimination? (I'm not too familiar with this code.) Jay. On 23 November 2015 at 13:07, Jay Foad

Hi Rafael, is there a repository with the static pages or should I simply produce a diff between the 2 versions? Regards, Kai On 03.12.2013 14:30, Rafael Espíndola wrote: > Can you send a patch? > > On 2 December 2013 06:44, Kai Nacke <kai at redstar.de> wrote: >> Hi! >> >> I like to submit some updates to the LLVM website regarding the LDC >> compiler.

I think that this page needs a TOC: http://wiki.centos.org/HowTos/Nagios Akemi