From: Stephen W. <st...@ic...> - 2019-10-14 21:09:49
|
The $fatal() task prints a standard message, and allows the user to include other data. The standard does say that the simulator should return an error, and with this patch I have in mind, it would wind up replacing $finish_and_return(1) for you. I just want to make sure nobody gets caught off guard in a bad way if I apply this patch. On Mon, Oct 14, 2019 at 1:48 PM Niels Möller <ni...@ly...> wrote: > > Stephen Williams <st...@ic...> writes: > > > I have a bug report for Icarus Verilog requesting that $fatal cause > > the vvp program to return EXIT_FAILURE or some-such, instead of > > EXIT_SUCCESS like all other variants of $finish. > > In my verilog test programs, I currently use $finish_and_return(1) to > indicate failure to the test driver script. If that can be replaced with > $fatal (which I take is more standard?), that would be nice. > > How do other simulators implement $fatal? If Icarus departs from > conventions by returning EXIT_FAILURE, then I would better stay with > $finish_and_return(1) which will fail in a more obvious way if not using > Icarus. > > Regards, > /Niels > > -- > Niels Möller. PGP-encrypted email is preferred. Keyid 368C6677. > Internet email is subject to wholesale government surveillance. -- Steve Williams "The woods are lovely, dark and deep. st...@ic... But I have promises to keep, http://www.icarus.com and lines to code before I sleep, http://www.picturel.com And lines to code before I sleep." |