search for: __sparc

Hello, The current version in SVN fails to compile in sparc machines since gcc defines "sparc" as a macro in sparc machines that expands to 1 (see below) but Triple.h defines "sparc" as a enum constant. $ cpp -dM /dev/null | grep sparc #define sparc 1 #define __sparc__ 1 #define __sparc 1 The attached patch fixes this problem by renaming sparc to sparc_. Thanks, Venkatraman -------------- next part -------------- A non-text attachment was scrubbed... Name: llvm-compile-in-sparc.patch Type: application/octet-stream Size: 4049 bytes Desc: not available URL: &...

...rent version in SVN fails to compile in sparc machines since > gcc defines "sparc" as a macro in sparc machines that expands to 1 > (see below) but Triple.h defines "sparc" as a enum constant. > > $ cpp -dM /dev/null | grep sparc > #define sparc 1 > #define __sparc__ 1 > #define __sparc 1 > > The attached patch fixes this problem by renaming sparc to sparc_. the same thing happens with mips: "mips" is defined to be a numerical value on mips machines, and this breaks Triple.h. Ciao, Duncan.

...ls to compile in sparc machines since >> gcc defines "sparc" as a macro in sparc machines that expands to 1 >> (see below) but Triple.h defines "sparc" as a enum constant. >> >>  $ cpp -dM /dev/null | grep sparc >>  #define sparc 1 >>  #define __sparc__ 1 >>  #define __sparc 1 >> >>  The attached patch fixes this problem by renaming sparc to sparc_. > > the same thing happens with mips: "mips" is defined to be a numerical > value on mips machines, and this breaks Triple.h. > > Ciao, > > Duncan. &g...

...e less likely to >> collide. I think just upcasing them might be good enough? > > It should, this is the pattern generally emitted by all of the backends. > >>>> >>>>  $ cpp -dM /dev/null | grep sparc >>>>  #define sparc 1 >>>>  #define __sparc__ 1 >>>>  #define __sparc 1 > > There's likely an all uppercase one as well, but afaik no camel case one. > > -eric >

...ename the constants to be a little less likely to > collide. I think just upcasing them might be good enough? It should, this is the pattern generally emitted by all of the backends. >>> >>> $ cpp -dM /dev/null | grep sparc >>> #define sparc 1 >>> #define __sparc__ 1 >>> #define __sparc 1 There's likely an all uppercase one as well, but afaik no camel case one. -eric

...llide. I think just upcasing them might be good enough? >> >> It should, this is the pattern generally emitted by all of the backends. >> >>>>> >>>>>  $ cpp -dM /dev/null | grep sparc >>>>>  #define sparc 1 >>>>>  #define __sparc__ 1 >>>>>  #define __sparc 1 >> >> There's likely an all uppercase one as well, but afaik no camel case one. >> >> -eric >> >

I would like to know how to get access to errno when using pid provider to probe calls to libc functions like fopen(). The built-in errno appears to be only for system calls. What I''d like to be able to do is investigate where in an application I''m encountering EMFILE and what the stack looks like at the time. This message posted from opensolaris.org