search for: l6g

...e="font-family:Arial,Helvetica,sans-serif;" ><font size="2" ><span style="font-size:0.857em;" >Kit Barton, Ph.D.<br>STSM, Technical lead for LLVM on Power and XL Compilers<br>IBM Toronto Lab, C2/705/8200/MKM<br>8200 Warden Ave, Markham, L6G 1C7<br>(905) 413-3452<br>kbarton@ca.ibm.com</span></font></span></font></font></div></div></div></div></div></div></div><BR>

Hi, I am wondering why we dont support PPC32 LE? Here is the output of llvm-mc --version, in which only PPC32, PPC64 & PPC64LE are supported. $ llvm-mc --version LLVM (http://llvm.org/): LLVM version 3.6.2 Optimized build with assertions. Built Aug 2 2015 (11:39:46). Default target: x86_64-apple-darwin15.4.0 Host CPU: core-avx2 Registered Targets: aarch64 - AArch64

...growth. For example, it may not be advantageous to do this if the simplified branch is cold. If anyone has any comments/suggestions we are very much interested in hearing them. Regards, Tony Jiang, M.Sc. LLVM PPC Backend Development IBM Toronto Lab, C2/712/8200/MKM 8200 Warden Ave, Markham, L6G 1C7 Email: jtony at ca.ibm.com Phone: 905-413-3676 -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20170831/3fef8743/attachment.html>

Greetings, I''ve had no success with mounting a vfat file system created by a Windows XP guest on a lvm volume. # mount -t vfat /dev/vg1/win1 /mnt/ mount: wrong fs type, bad option, bad superblock on /dev/vg1/win1, missing codepage or other error In some cases useful info is found in syslog - try dmesg | tail or so # dmesg FAT: invalid media value (0xb9) VFS:

...ee that SE should be always available to a LoopNest pass. The > LoopNest analysis should be available to a LoopNest pass manager, and a > LoopNest pass IMO should operate on a LoopNest IR unit rather than a Loop. > > Ettore Tiotto > IBM Canada Laboratory, 8200 Warden Ave, Markham, ON L6G 1C7, Canada > etiotto at ca.ibm.com -- Phone: (905) 413-2387 > > “No great discovery was ever made without a bold guess.” - Isaac Newton > > > > ----- Original message ----- > From: Whitney T Tsang/Toronto/IBM > To: Ta-Wei Tu <tu.da.wei at gmail.com> > Cc: llvm-d...

Hi everyone, The OpenMP standards committee has begun work to formalize their memory model, and define its relationship to the C/C++ memory models. A questionnaire has been put together (pasted below), and I'd like everyone's help in composing detailed answers to inform their decision-making process. While our OpenMP support is still in active development, many of these questions apply

Hi, Thanks for your help! I've checked the sources that you mentioned. Currently, I think that I would need to implement a FunctionToLoopNestPassAdaptor which is essentially the same as the FunctionToLoopPassAdaptor but operates only on LI.getTopLevelLoops(). We might also need a LNPMUpdater (LoopNestPassManagerUpdater) which disallows adding inner-loops back into the pipeline, and

I found a bit weird to use address space for this, since the offset of getting stack_guard in TCB is, unfortunately, negative: https://github.com/gcc-mirror/gcc/blob/master/gcc/config/rs6000/linux64.h#L610 In my understanding an address space is referring to a segment register (-on powerpc 32bit; or SLB entry on powerpc 64bit?) with a non-negative offset value, so that it's actually accessing