*stares at yosys bug, tries hard to avoid touching http://genrtlil.cc , eventually gives up and opens it, in write mode* gods help me
-
Show this thread
-
WAIT WHAT, THE VERILOG FRONTEND ALLOWS YOU TO CALL ARBITRARY C FUNCTIONS AT ELABORATION TIME JUST LIKE THAT, BY DESIGN?!?
2 replies 0 retweets 14 likesShow this thread -
Replying to @mwk4
at what point do you require executable bit to be set on .v files
1 reply 0 retweets 1 like -
Oh, I really like that idea!
Are we technically still conforming with the LRM if we require execute permission on the verilog file for DPI-C?
We already have -nodpi to disable it altogether. We could add -dpi and check for execute permission if neither is present.2 replies 0 retweets 3 likes
That being said, it's practically guaranteed that we still have exploitable memory bugs in the front-end.
We found (and fixed) a few when we ran AFL on the front-end but I'm sure there are plenty more left.
(However, that code has extremely strong "security by obscurity"
)
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.