02-03-2009
GCC version is
>> gcc -v
Reading specs from /usr/lib/gcc/x86_64-redhat-linux/3.4.4/specs
Configured with: ../configure --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --enable-shared --enable-threads=posix --disable-checking --with-system-zlib --enable-__cxa_atexit --disable-libunwind-exceptions --enable-java-awt=gtk --host=x86_64-redhat-linux
Thread model: posix
gcc version 3.4.4 20050721 (Red Hat 3.4.4-2)
7 More Discussions You Might Find Interesting
1. Programming
Hello,
If i have 2 strings str1 and str2, i would like to copy/concatenate str2 to str1, from 1st bit leaving the 0th bit.
How do i do it? (2 Replies)
Discussion started by: jazz
2 Replies
2. AIX
Hi all,
I am facing problem in porting to 64 bit AIX especially with compiling options to compile and run under 64 bit kernel.Can any one put some light on the issue
thanks in advance
vishal (14 Replies)
Discussion started by: vishalzone2002
14 Replies
3. Solaris
Hi,
I am trying to convert 32-bit code to 64-bit.
I have defined function
int main()
{
int* l;
size_t len1;
fun(len1);
return 0;
}
void fun(int* ptr)
{
cout<<"\nsizeof(ptr)"<<sizeof(ptr);
}
However while compiling getting error as :
Error: Formal argument ptr... (2 Replies)
Discussion started by: amit_27
2 Replies
4. SuSE
Dear All,
I am trying to build my code (currently functioning on 32bit) on 64 bit SUSE machine.
I am getting following error:
warning: initializer element is not computable at load time
dau.gss.c:275: error: initializer element is not constant
dau.gss.c:275: error: (near initialization for... (10 Replies)
Discussion started by: skaushal.schip
10 Replies
5. UNIX for Advanced & Expert Users
Hi,
I am compiling Qt-4.7 for 32-bit on 64-bit (x86_64) Ubuntu 8.04 desktop. I have installed all the 32-bit libraries (/lib32 and /usr/lib32) through getlibs and "apt-get install ia32-libs". But I am getting the following error while configuring the qt project as:
./configure -platform... (2 Replies)
Discussion started by: royalibrahim
2 Replies
6. Shell Programming and Scripting
Hi,
Here is the issue. From the program snippet I have Base: 0x1800000000, Size: 0x3FFE7FFFFFFFF which are of 40 and 56 bits. SO I used use bignum to do the math but summing them up I always failed having correct result.
perl interpreter info,
perl, v5.8.8 built for... (0 Replies)
Discussion started by: rrd1986
0 Replies
7. Windows & DOS: Issues & Discussions
Hello everyone.
I bought a dell laptop (XPS M1330) online which came without a hard drive. There is a Windows Vista Ultimate OEMAct sticker with product key at the bottom case. I checked dell website (here) for this model and it says this model supports both 32 and 64-bit version of Windows... (4 Replies)
Discussion started by: milhan
4 Replies
GETCPU(2) Linux Programmer's Manual GETCPU(2)
NAME
getcpu - determine CPU and NUMA node on which the calling thread is running
SYNOPSIS
#include <linux/getcpu.h>
int getcpu(unsigned *cpu, unsigned *node, struct getcpu_cache *tcache);
DESCRIPTION
The getcpu() system call identifies the processor and node on which the calling thread or process is currently running and writes them into
the integers pointed to by the cpu and node arguments. The processor is a unique small integer identifying a CPU. The node is a unique
small identifier identifying a NUMA node. When either cpu or node is NULL nothing is written to the respective pointer.
The third argument to this system call is nowadays unused.
The information placed in cpu is only guaranteed to be current at the time of the call: unless the CPU affinity has been fixed using
sched_setaffinity(2), the kernel might change the CPU at any time. (Normally this does not happen because the scheduler tries to minimize
movements between CPUs to keep caches hot, but it is possible.) The caller must be prepared to handle the situation when cpu and node are
no longer the current CPU and node.
VERSIONS
getcpu() was added in kernel 2.6.19 for x86_64 and i386.
CONFORMING TO
getcpu() is Linux specific.
NOTES
Linux makes a best effort to make this call as fast possible. The intention of getcpu() is to allow programs to make optimizations with
per-CPU data or for NUMA optimization.
Glibc does not provide a wrapper for this system call; call it using syscall(2); or use sched_getcpu(3) instead.
The tcache argument is unused since Linux 2.6.24. In earlier kernels, if this argument was non-NULL, then it specified a pointer to a
caller-allocated buffer in thread-local storage that was used to provide a caching mechanism for getcpu(). Use of the cache could speed
getcpu() calls, at the cost that there was a very small chance that the returned information would be out of date. The caching mechanism
was considered to cause problems when migrating threads between CPUs, and so the argument is now ignored.
SEE ALSO
mbind(2), sched_setaffinity(2), set_mempolicy(2), sched_getcpu(3), cpuset(7)
COLOPHON
This page is part of release 3.27 of the Linux man-pages project. A description of the project, and information about reporting bugs, can
be found at http://www.kernel.org/doc/man-pages/.
Linux 2008-06-03 GETCPU(2)