similar to: [LLVMdev] arch-specific predefines in LLVM's source

Displaying 20 results from an estimated 700 matches similar to: "[LLVMdev] arch-specific predefines in LLVM's source"

2013 Jul 26
2
[LLVMdev] arch-specific predefines in LLVM's source
> ----- Original Message ----- >> Hi all, >> My recent commit r187027 fixed a simple oversight of forgetting to >> check for __ppc__ (only checking __powerpc__), which broke my >> powerpc-apple-darwin8 stage1 tests, since the system gcc only >> provided >> __ppc__. I was wondering if this justifies using simpler macros like >> >> #define
2013 Jul 27
1
[LLVMdev] arch-specific predefines in LLVM's source
Hi, > ----- Original Message ----- >>> ----- Original Message ----- >>>> Hi all, >>>> My recent commit r187027 fixed a simple oversight of forgetting >>>> to >>>> check for __ppc__ (only checking __powerpc__), which broke my >>>> powerpc-apple-darwin8 stage1 tests, since the system gcc only >>>> provided
2013 Jul 27
0
[LLVMdev] arch-specific predefines in LLVM's source
----- Original Message ----- > > ----- Original Message ----- > >> Hi all, > >> My recent commit r187027 fixed a simple oversight of forgetting > >> to > >> check for __ppc__ (only checking __powerpc__), which broke my > >> powerpc-apple-darwin8 stage1 tests, since the system gcc only > >> provided > >> __ppc__. I was
2013 Jul 26
0
[LLVMdev] arch-specific predefines in LLVM's source
----- Original Message ----- > Hi all, > My recent commit r187027 fixed a simple oversight of forgetting to > check for __ppc__ (only checking __powerpc__), which broke my > powerpc-apple-darwin8 stage1 tests, since the system gcc only > provided > __ppc__. I was wondering if this justifies using simpler macros like > > #define LLVM_PPC (defined(__ppc__) ||
2008 Jun 16
6
[LLVMdev] PowerPC instruction cache invalidation
Hi all, When you genetate code on PowerPC you need to explicitly invalidate the instruction cache to force the processor to reread it. In LLVM there is code to do this for function stubs on Macintosh, but not for other platforms and not for JITted code generally. The attached patch adds support for GNU platforms, but I can't figure out a nice way to call it for all generated code. Can
2008 Jun 16
0
[LLVMdev] PowerPC instruction cache invalidation
On Mon, 16 Jun 2008, Gary Benson wrote: > When you genetate code on PowerPC you need to explicitly invalidate > the instruction cache to force the processor to reread it. In LLVM > there is code to do this for function stubs on Macintosh, but not > for other platforms and not for JITted code generally. Applied, thanks!
2008 May 22
1
[LLVMdev] [PATCH] fix for FreeBSD/powerpc build breakage
All, The following patch fixes the build breakage on FreeBSD/powerpc: Index: lib/Target/PowerPC/PPCJITInfo.cpp =================================================================== --- lib/Target/PowerPC/PPCJITInfo.cpp (revision 51432) +++ lib/Target/PowerPC/PPCJITInfo.cpp (working copy) @@ -72,7 +72,7 @@ extern "C" void PPC64CompilationCallback(); #if (defined(__POWERPC__) ||
2008 Jun 17
1
[LLVMdev] PowerPC instruction cache invalidation
Chris Lattner wrote: > On Mon, 16 Jun 2008, Gary Benson wrote: > > When you genetate code on PowerPC you need to explicitly > > invalidate the instruction cache to force the processor to reread > > it. In LLVM there is code to do this for function stubs on > > Macintosh, but not for other platforms and not for JITted code > > generally. > > Applied, thanks!
2010 Sep 29
1
location of Rconfig.h when using architecture-dependent subdirs
Hello, I just tried configuring R to use architecture-dependent subdirs $ r_arch=x86_64 ./configure --prefix=/u/smat/konis/testdir on a Debain Squeeze box $ uname -a Linux smapc007 2.6.32-5-686 #1 SMP Sat Sep 18 02:14:45 UTC 2010 i686 GNU/Linux After building and installing, the Rconfig.h ended up in .../lib/R/include/x86_64 but R.h still includes it as #include <Rconfig.h>
2019 Dec 17
2
Build failure on powerpc64
>>>>> Tom Callaway >>>>> on Fri, 13 Dec 2019 11:06:25 -0500 writes: > An excellent question. It is important to remember two key > facts: > 1. With gcc on ppc64, long doubles exist, they can > be used, just not safely as constants (and maybe they > still can be used safely under specific conditions?). > 2. I am not an
2020 Mar 25
1
Build failure on powerpc64
Do note that 3.6-patched will only be live for a day or two as we branch for 4.0.0 on Friday. Anything committed there is unlikely to make it into an official release (in principle, the 3.6 branch can be revived but it would take a very strong incentive to do so.) If you want an R-3.6.3-for-ppc, I think a vendor patch is the way. AFAIR (it's been more than a decade since I looked at this
2008 Apr 26
4
how to use printk() in xen?
hi, all: i want to add a function in xen. in the function i need to call the "printk" to display the values of some variables. i found the definition of printk() in file "xen-3.1.0-src\xen\include\xen\lib.h ": extern void printk(const char *format, ...) __attribute__ ((format (printf, 1, 2))); who can tell me the location of printk()? thanks in advance. 2008-04-26
2011 Dec 16
3
[LLVMdev] llvm/clang test failures on powerpc-darwin8
Hi, Thanks for the quick reply again. > On Thu, Dec 15, 2011 at 1:17 PM, David Fang <fang at csl.cornell.edu> wrote: >> Hi, >> >> I've bootstrapped llvm/clang from svn-trunk on powerpc-darwin8 (g++-4.0.1), and >> have the following test results to share. >> Summary below, full log at: >>
2020 Jun 02
2
Improve hot cold splitting to aggressively outline small blocks
Hello Tobias, Thank you for the suggestion! Aditya also mentioned this. I will look into it. Best regards, Ruijie Ruijie Fang Email: ruijief at princeton.edu On Tue, Jun 2, 2020 at 12:48 PM Tobias Hieta <tobias at plexapp.com> wrote: > Hello Ruijie, > > One other workload that would be interesting to test might be clang > itself. Building clang with PGO information is a
2012 Jan 17
2
[LLVMdev] powerpc-darwin8 build/test status page
Hi, For anyone who might be interested, I've thrown together a little page to track my builds of llvm and clang, both release 3.0 and svn-trunk, on powerpc-darwin8. http://www.csl.cornell.edu/~fang/sw/llvm/ I'll update the list of logs each time I svn-update and build. It's nowhere as nice as a real buildbot page, but it's better than nothing. 3.0 still has over 20 test
2011 Dec 16
3
[LLVMdev] llvm/clang test failures on powerpc-darwin8
>> These results have far fewer failures than svn-trunk, and are also >> comparable to bootstrapping with gcc-4.6.2, summarized here: >> http://paste.lisp.org/display/126363 >> (Unfortunately, I no longer have the whole build/test log for the gcc46 bootstrap.) >> This consistency between different bootstraps of the release gives me >> some hope that g++-4.0.1 is
2012 Jan 18
1
[LLVMdev] [cfe-dev] powerpc-darwin8 build/test status page
18.01.2012, 02:46, "David Fang" <fang at csl.cornell.edu>: > Hi, >          For anyone who might be interested, I've thrown together a little > page to track my builds of llvm and clang, both release 3.0 and > svn-trunk, on powerpc-darwin8. > > http://www.csl.cornell.edu/~fang/sw/llvm/ > > I'll update the list of logs each time I svn-update and
2012 Jan 18
0
[LLVMdev] [cfe-dev] powerpc-darwin8 build/test status page
On Wed, Jan 18, 2012 at 10:51:38PM +0400, Konstantin Tokarev wrote: > > > 18.01.2012, 02:46, "David Fang" <fang at csl.cornell.edu>: > > Hi, > > ?????????For anyone who might be interested, I've thrown together a little > > page to track my builds of llvm and clang, both release 3.0 and > > svn-trunk, on powerpc-darwin8. > > > >
2004 Jan 30
3
memory problem for R
Hi, I try to use lm to fit a linear model with 600k rows and 70 attributes. But I can't even load the data into the R environment. The error message says the vector memory is used up. Is there anyone having experience with large datasets in R? (I bet) Please advise. thanks, Yun-Fang [[alternative HTML version deleted]]
2003 Dec 20
7
error bars around a point
All Is there an R command to produce error bars around a plotted point. Crawley's book uses the command error.bar() but my version of R rejects it. Must be an S+ command(?). Thanks REX [[alternative HTML version deleted]]