fpga

Our users are often confused by the output from programs such as zip2john sometimes being very large (multi-gigabyte). Maybe we should identify and enhance these programs to output a message to stderr to explain to users that it's normal for the output to be very large - maybe always or maybe only when the output size is above a threshold (e.g., 1 million bytes?)

paddle-mobile将开发一个新的版本，为了：

• 支持Paddle Fluid
• 更小的体积
• 更快的速度
• 更广泛地支持各种arm设备和终端平台

因此，paddle-mobile将会进行一次完全的重构，从框架设计到代码开发。在新版本开发完成后，将会删除原有mobile-deep-learning的代码。新版本开发期间，代码将放置在paddle-mobile repo的一个子目录下。对于子目录的命名，目前有3个候选，希望大家投票：

• 👍 zygote
• 👎 paddle
• ❤️ fluid

有更好的建议，请回复issue。相关issue：#121
另外，待新版本代码开发完成，移除老版本mobile-deep-learning代码后，新版本代码将移出子目录，直接放置在paddle-mobile repo下面。

I'm not sure about if it was a system configuration problem on my computer. Most of my computers runs Archlinux with Java 18. It seems the pin text of RAM is too large and overlaps each other:

While I didn't found a way to configure font of the canvas in menus. I found that a modifica

If this is not the case a page fault should be generated. Right now we generate an instruction access fault.

https://github.com/pulp-platform/ariane/blob/ad70ce1f30dad539e5a365ffe71a02aaf20b397e/src/load_store_unit.sv#L339

Add Javadoc to document the examples in TornadoVM.

This affects the packages under the examples module:

https://github.com/beehive-lab/TornadoVM/tree/master/examples/src/main/java/uk/ac/manchester/tornado/examples

The documentation is at the class-level and it will contain a description of how the TornadoVM API is used for each example. Additionally, it contains how to run the example

If you speak another language, I would appreciate your help in translating the README.md.

For tables, checklists, or other data that might change, please indicate that that information is in the main README. Otherwise every change to the main README will need to be replicated to the other READMEs.

^ I've tried to do this a bit in the French README. The only thing you need to replicate when

Tuo Xie requested the ability to visualize clocking (pins & wires I believe). We should make it easier to visualize subsets of the device routing resource and types of routing nets.

Proposed Behaviour

Add filtering to the rr_nodes displayed (ToggleRR), and to the nets displayed (ToggleNets). I think we should have an option to filter what is shown by node type, node name (segment or pin t