开云体育

Kudos to bluespec for consistent semantics... I tried to use RWire within the module such that you had to call the following in the same rule to retire a tag: ``` tagEngine.setTagToRetire

That might be OK if it can all happen in the same cycle

Another option is to have two separate methods: one that takes the argument and returns if it's ok, and a method that can then be called to do the action. J <programmed4jesus@...>

I don't believe there is a way to surgically suppress the warning. If you have thoughts on how you would want to specify it, that would be a reasonable enhancement request. I can imagine allowing an

So I suppose my only option is to have the method indicate whether or not the transaction was successful.

It is intentional. The logical order of events for a method is that the RDY is available first, then the arguments are provided (and an EN signal, if it's an action), and then the return value is

Un-commenting the commented-out lines in the snippet

Interestingly, the BSV parser can insert implicit "_read" method calls in more places than BH. For example, "tagVec[0]" can be used for the register value. I don't recall offhand why this works, but

<programmed4jesus@...> wrote: The BSV parser desugars into BH code, so if you're familiar with BH or Haskell, it may be helpful to mentally think of the BSV code in those terms.

Hi all! Hopefully this is the right place to post this, and I hope you don't mind a *tiny* bit of self advertising: I decided to take the initiative to create a Discord server and a SubReddit for

The bsc library has a function ?'readVReg :: Vector n (Reg a) -> Vector n a' which performs _read on each register in a vector of registers and returns a vector of the values. There is also

So the error message is telling you what the problem is: your vector has `Reg ...` inside, and so if you take an element from that vector with `!!` then you get back a thing of type `Reg ...`, which

The `$display (fshow (tagVec !! 0))` found here ( https://git.joyofhardware.com/ReferenceProjects/riscv-bluespec-classic/src/commit/ac48f5a4adeea1cbcd7b472db88d666d89942dca/bs/TagEngine.bs#L57 ) is

I've updated my example so it is parameterized. Note, it's parameterized both on the vector length and on the bit-width of each register. The example shows two instances of vector-of-registers, with

I think I eventually made progress on the previous issue... So in BH RN I have the following where the number of bits in `UInt` is parameterizable: data Tag a = Next ( UInt a) | Empty deriving ( Bits

Thanks for that code! I'm wondering how I can make it parametrizable... So far - no luck! import Vector ::*; // Required for Vector module mkTop #(parameter Integer bitWidth ) (Empty); // No default

Here's how I'd write it in BSV; I'd guess it's not too different in BH (would use the same mapM and genVector). Example run: ./exe_HW_bsim v_rgs [ 0] = 0 v_rgs [ 1] = 1 v_rgs [ 2] = 2 v_rgs [ 3]

I'm trying to figure out how to programmatically create a vector of registers in Bluespec Haskell initialized from 0..5. I think I should use mapM with mkReg next - but I'm not quite sure... Any help

NVM - I think I figured it out

I also like the idea. Always found such lists really useful in other languages/frameworks. Johannes