Sponsored Content
Top Forums Programming Bitwise operation for state machine Post 302880859 by Don Cragun on Tuesday 24th of December 2013 05:07:18 AM
Old 12-24-2013
So you have a variable (e.g. state) that presumably should always have no more than one of the three low order bits set. (Or, maybe you mean it should always have exactly one of the three low order bits set. Your specification is ambiguous as to which of these you mean.)

How will you tell your machine to change state?
Will you call a function to change the state? If so, why is that function not just an assignment to state? Is it that you want to verify that the requested new state has no more than one (or exactly one) of the three low order bits set?

Maybe you want a function that takes two arguments, states to add to state and states to remove from state.

What language are you using? (I could guess C, but it isn't the only language that includes enums.)

What have you tried so far?
 

2 More Discussions You Might Find Interesting

1. AIX

Open firmware state to running state

Hi Admins, I am having a whole system lpar in open firmware state on HMC. How can I bring it to running state ? Let me know. Thanks. (2 Replies)
Discussion started by: snchaudhari2
2 Replies

2. Shell Programming and Scripting

Vim function to generate RTL Code(finite state machine) in verilog

Hi I wanted to call the AutoFsm function (given below) in vim to generate a code something like: **********verilog code to generate ************* always @(posedge clk or negedge rst_n) begin if(!rst_n) begin state_r <= #1 next_stateascii_r; ... (0 Replies)
Discussion started by: dll_fpga
0 Replies
random(3)						     Library Functions Manual							 random(3)

Name
       random, srandom, initstate, setstate - better random number generator; routines for changing generators

Syntax
       long random()

       void srandom(seed)
       int seed;

       char *initstate(seed, state, n)
       unsigned seed;
       char *state;
       int n;

       char *setstate(state)
       char *state;

Description
       The  subroutine	uses  a  non-linear additive feedback random number generator employing a default table of size 31 long integers to return
       successive pseudo-random numbers in the range from 0 to (2**31)-1.  The period of this random number generator is very large, approximately
       16*((2**31)-1).

       The  subroutines  have  (almost)  the same calling sequence and initialization properties as The difference is that rand(3) produces a much
       less random sequence - in fact, the low dozen bits generated by rand go through a cyclic pattern.  All the bits generated  by  are  usable.
       For example, "random()&01" will produce a random binary value.

       Unlike  does  not  return  the  old seed; the reason for this is that the amount of state information used is much more than a single word.
       (Two other routines are provided to deal with restarting/changing random number generators.)  Like  however,  will  by  default	produce  a
       sequence of numbers that can be duplicated by calling with 1 as the seed.

       The  routine  allows  a state array, passed in as an argument, to be initialized for future use.  The size of the state array (in bytes) is
       used by to decide how sophisticated a random number generator it should use - the more state, the better the random numbers will be.  (Cur-
       rent  "optimal"	values	for  the  amount of state information are 8, 32, 64, 128, and 256 bytes; other amounts will be rounded down to the
       nearest known amount.  Using less than 8 bytes will cause an error).  The seed for the initialization (which specifies a starting point for
       the  random  number  sequence, and provides for restarting at the same point) is also an argument.  returns a pointer to the previous state
       information array.

       Once a state has been initialized, the routine provides for rapid switching between states.  The subroutine returns a pointer to the previ-
       ous state array; its argument state array is used for further random number generation until the next call to or

       Once  a	state  array  has  been  initialized, it may be restarted at a different point either by calling (with the desired seed, the state
       array, and its size) or by calling both (with the state array) and (with the desired seed).  The advantage of calling both and is that  the
       size of the state array does not have to be remembered after it is initialized.

       With  256  bytes  of  state information, the period of the random number generator is greater than 269, which should be sufficient for most
       purposes.

Diagnostics
       If is called with less than 8 bytes of state information, or if detects that the state information has been  garbled,  error  messages  are
       printed on the standard error output.

See Also
       rand(3)

																	 random(3)
All times are GMT -4. The time now is 11:38 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy