There is a bad link on the master branch readme (https://github.com/golang/dep/blob/master/README.md) in the section for Windows users looking to download dep.

The link is bolded in this sentence below and currently points to https://go.equinox.io/github.com/golang/dep/cmd/dep which returns a 404 code

• On Windows, you can download a tarball from go.equinox.io.

Red/System []
s2: declare struct! [
   a   [integer!]
   b   [c-string!]
   c   [struct! [d [integer!] e [float!]] value]
]
probe size? s2

Taken from https://static.red-lang.org/red-system-specs.html#section-4.7.2
Says:

Compiling to native code...
*** Red/System Compiler Internal Error: Script Error : last expected series argument of type: series port tuple
*** Where: for

Before you submit an issue we recommend you drop into the Gitter community and ask any questions you have or mention any problems you've had getting started with the server.

Please provide as much information as you can with this issue report. If you believe it may be an issue with one of the client libraries please report it on their [own trackers](https:

Is this a feature or a bug?

• Feature
• Bug

Please describe the actual behavior.

Currently rush uses a fixed commit message during the rush version --bump workflow:

https://github.com/microsoft/rushstack/blob/626c8efae811650d9eb778386f31ffb393b43468/apps/rush-lib/src/cli/actions/VersionAction.ts#L215

**If the issue is a bug, how can we reproduce it? Please provide

grep unknown opentitan.fasm  | wc
    557    6127   52651

557 bits isn't too many. Most of these are likely related to the DSP, as 1 DSP is being used:

DSP_L_X66Y110.DSP48.DSP_0.AREG_0
DSP_L_X66Y110.DSP48.DSP_0.BREG_0
DSP_L_X66Y110.DSP48.DSP_0.MASK[45:0] = 46'b1111111111111111111111111111111111111111111111
DSP_L_X66Y110.DSP48.DSP_0.ZADREG[0]
DSP_L_X66Y110.DSP48.DSP_0.ZAL

Basically, everything shown in Intel's intrinsic guide that we support should be usable, which, afaik, we're doing only SSE & MMX (because MMX is before SSE, we should still have it there if people really want it or happen to have been using it).

This shouldn't be TOO difficult, mostly just tedious, and it might be smart to do #

Garbage collect should be a standard Fileioc function.
I would also suggest a function that would tell you when a garbage collect would be necessary.
I assume this is just about calculating the largest free memory space in archive, let me know if I'm wrong.

There are a lot of variables in hal/video.c which should be static.

https://github.com/XboxDev/nxdk/blob/ce8da0b9cf93a6ce0051a7a2399cfdb93771e6ea/lib/hal/video.c#L36-L42
https://github.com/XboxDev/nxdk/blob/ce8da0b9cf93a6ce0051a7a2399cfdb93771e6ea/lib/hal/video.c#L61-L62
https://github.com/XboxDev/nxdk/blob/ce8da0b9cf93a6ce0051a7a2399cfdb93771e6ea/lib/hal/video.c#L121

Some of this intera

Context

Readme.pod is written in Perl 5 pod. It fails with:

perl6 --doc README.pod 
===SORRY!=== Error while compiling /home/jmerelo/Code/forks/perl6/zef/README.pod
Preceding context expects a term, but found

Vendor tools dram tests were not enabled until #1234 got merged.

With SymbiFlow/symbiflow-arch-defs#1268 I have temporarily disabled the vivado_targets, to let CI go green (as it has been red for too long now).

This issue is to keep track of the problem with DRAM evaluated on vendor tools with fasm2bels.

Implement (or extend the current logger) to support CSV output.

I may be missing something but other toolchains seem to support thin_lto or other forms of LTO (https://github.com/tensorflow/tensorflow/blob/1843f39c11e42751837c62acfb74e1fe697353ef/third_party/toolchains/clang6/CROSSTOOL.tpl#L402 for example) -- it would be lovely to support that here. Or perhaps I'm mistaken: can someone suggest how I might enable LTO/pgo in general?