From: | "Derek M. Jones" <derek@_NOSPAM_knosof.co.uk> |
Newsgroups: | comp.compilers |
Date: | Wed, 8 May 2019 19:08:33 +0100 |
Organization: | virginmedia.com |
References: | 19-04-021 19-04-023 19-04-037 19-04-039 19-04-042 19-04-044 19-04-047 19-05-004 19-05-006 19-05-016 19-05-020 19-05-024 19-05-025 19-05-028 19-05-029 19-05-034 19-05-045 19-05-057 19-05-060 |
Injection-Info: | gal.iecc.com; posting-host="news.iecc.com:2001:470:1f07:1126:0:676f:7373:6970"; logging-data="4527"; mail-complaints-to="abuse@iecc.com" |
Keywords: | tools |
Posted-Date: | 08 May 2019 15:11:08 EDT |
In-Reply-To: | 19-05-060 |
Content-Language: | en-US |
David,
> In C, what I coded was buggy - it has no defined behaviour. What /I/
> want the compiler to do, is warn me about it. (gcc doesn't, at least
> not with the flags I tried. Maybe next version will - I always hope for
> better warnings.) And I want the compiler to assume that I am not
You might like to give Cerberus a go:
http://cerberus.cl.cam.ac.uk/cerberus
To cover all cases, click Options and untick
Sequentialise operations (soon to be the default, I'm told).
--
Derek M. Jones
blog:shape-of-code.coding-guidelines.com
Return to the
comp.compilers page.
Search the
comp.compilers archives again.