Concurrent bsc invocations using same build dir interfere with one another

[b-lang-org]

Concurrent bsc invocations using same build dir interfere with one another

[quark17]

I see that you've submitted a PR for this. Thank you, I'll review it. BSC should definitely be generating a unique name.

For years, the only supported syntax was BSV, because the target users were hardware designers that were familiar with Verilog and SystemVerilog, not Haskell. The Haskell-based "Classic" syntax (which we're now calling BH) was maintained, but new features weren't added to it and nearly no one wrote designs in it. The BSV syntax natively supports SystemVerilog preprocessor directives (it preserves position information etc) and so I don't think anyone ever used CPP, instead preferring the SV PP. The Classic/BH syntax obviously doesn't have SV preprocessor support, so you have to use CPP. Recently, there's been interest in using the Classic/BH syntax, and those Classic/BH tutorial examples were added to help those folks. I assume that as more people start using the BH front-end, we'll see requests for fixes like this and for features (to make the BH front-end catch up with the BSV front-end).

[cbiffle]

That's a great point that this affects only the "classic" frontend. I didn't realize that (as I've been working with classic).

I think I've seen this bug manifest without -cpp on the command line, but I'm going to have to check my notes carefully before I assert that more forcefully.

[quark17]

The _t_o_p.c name should be fixed with commit e5af869. Do any other interferences occur?

[bpfoley]

@cbiffle Gentle poke... is this working for you now?

[quark17]

For reference: Above, I mentioned that I'd fixed it with commit e5af869, but I reverted that (with commit e0aab35) and accepted @cbiffle 's original solution for this (PR #52) with merge commit 8bcfc18.