-
Notifications
You must be signed in to change notification settings - Fork 39
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Target-specific defines for all files #40
Comments
micprog
referenced
this issue
in micprog/ibex
Nov 25, 2020
(double declaration of files pending https://github.com/fabianschuiki/bender/issues/40)
vogelpi
referenced
this issue
in lowRISC/ibex
Nov 26, 2020
(double declaration of files pending https://github.com/fabianschuiki/bender/issues/40)
vogelpi
referenced
this issue
in vogelpi/ibex
Jan 19, 2021
(double declaration of files pending https://github.com/fabianschuiki/bender/issues/40)
vogelpi
referenced
this issue
in vogelpi/ibex
Jan 21, 2021
(double declaration of files pending https://github.com/fabianschuiki/bender/issues/40)
paulsc96
pushed a commit
that referenced
this issue
Sep 10, 2022
* snitch_cluster: Fix ID mismatch on wide input * dma: Remove id module and fix reset value * dma: Mark DMA transactions as modifiable * testharness: Add DMA port into main memory * runtime: Add stdlib and only remove startfiles * sw/dma: Add DMA test * Move DMA functions to stand-alone compilation unit * Use FF macros for storage elements in DMA
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
To avoid doubly listing files, would it be possible to declare defines for all files depending on the target? As an example, this would allow for tracing-specific signals and blocks to be instantiated without using bender's standard
TARGET_***
defines. Syntax could be similar to below.The text was updated successfully, but these errors were encountered: