11-29-2011
Yes and no. They certainly can't do everything. They're very specialized for processing large batches of data, with very long pipelines.
This means they don't perform well when they have to branch a lot. That limits the amount of data that can be processed at once.
6 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hi everyone- I'm creating an asset database for our company and the previous person who worked on this began categorizing servers in this manner:
Hardware
Server
Windows (or Unix)
I stated that Windows and Unix are software, not hardware and don't describe the physical box in any way.... (4 Replies)
Discussion started by: robywar
4 Replies
2. What is on Your Mind?
By far, Doritos Nacho Cheesier are the best tasting chips, well at least too me.
Have you tried them?
What are your favorite chips? (5 Replies)
Discussion started by: Neo
5 Replies
3. UNIX for Dummies Questions & Answers
Hello - I have a folder that contains files from 2003 till 2010. I am trying to figure out a command that would seperate each years file and show me a count?
Even if i can find a command that would give me year by year count, thats good enough too.
Thanks (8 Replies)
Discussion started by: DallasT
8 Replies
4. Hardware
Hi,
I am trying to buy a netbook with Ubuntu pre-installed. I have looked for hours and have not found anything. Calls to Dell, HP, Toshiba have confirmed them NOT selling Ubuntu preloaded laptops. This leads me to look for a netbook that can handle Ubuntu.
Getting to the point... I think I... (4 Replies)
Discussion started by: mearex
4 Replies
5. War Stories
So there I was in the summer of 1968, 24 years old, single, good job, two year old car with only four payments left, working in the purchasing department of a medium sized manufacturer and getting a free lunch every day with a sales rep. And then they put up an internal job posting for 'Systems... (1 Reply)
Discussion started by: jgt
1 Replies
6. OS X (Apple)
Hi guys and gals...
Intel reportedly expects Apple to start the Mac's transition to ARM next year - 9to5Mac (0 Replies)
Discussion started by: wisecracker
0 Replies
LEARN ABOUT ULTRIX
emulate_branch
emulate_branch(3) Library Functions Manual emulate_branch(3)
Name
emulate_branch, execute_branch - branch emulation
Syntax
#include <signal.h>
emulate_branch(scp, branch_instruction)
struct sigcontext *scp;
unsigned long branch_instruction;
execute_branch(branch_instruction)
unsigned long branch_instruction;
Description
The function is passed a signal context structure and a branch instruction. It emulates the branch based on the register values in the
signal context structure. It modifies the value of the program counter in the signal context structure (sc_pc) to the target of the
branch_instruction. The program counter must initially be pointing at the branch and the register values must be those at the time of the
branch. If the branch is not taken the program counter is advanced to point to the instruction after the delay slot (sc_pc += 8).
If the branch instruction is a `branch on coprocessor 2' or `branch on coprocessor 3' instruction, calls to execute the branch in data
space to determine if it is taken or not.
Return Values
The function returns a 0 if the branch was emulated successfully. A non-zero value indicates the value passed as a branch instruction was
not a branch instruction.
The function returns non-zero on taken branches and zero on non-taken branches.
Restrictions
Since is only intended to be used by it does not check its parameter to see if in fact it is a branch instruction. It is really a stop gap
in case a coprocessor is added without the kernel fully supporting it (which is unlikely).
See Also
cacheflush(2), sigvec(2), signal(3)
RISC emulate_branch(3)