Bug 1267 – "crash-on-valid-code" and "crash-on-invalid-code" keywords?
Status
RESOLVED
Resolution
WONTFIX
Severity
enhancement
Priority
P5
Component
dlang.org
Product
D
Version
D2
Platform
All
OS
All
Creation time
2007-06-15T11:25:00Z
Last change time
2015-06-09T01:31:17Z
Assigned to
braddr
Creator
matti.niemenmaa+dbugzilla
Comments
Comment #0 by matti.niemenmaa+dbugzilla — 2007-06-15T11:25:17Z
Some issues filed for DMD (and possibly GDC as well) have code which cause compiler crashes without error messages. Currently we only have the "ice-on-valid-code" and "ice-on-invalid-code" keywords, but they imply that an ICE (Internal Compiler Error) was output. This isn't always the case, and some disambiguation may be in order.
I'm suggesting that "crash-on-valid-code" and "crash-on-invalid-code" (or equivalent) keywords be added. Alternatively, rename "ice-on-*" to such and add an "ice" keyword, so that crashing code could be marked with "crash-on-*", while ICE code could be marked with "crash-on-*, ice".
I can go through the trouble of checking and correcting all the keywords for the current "ice-on-*" bugs, if that's an issue.
(I'm not sure if this would be of much use, but I always feel I'm misbehaving when I tag a bug with "ice-on-*" when there's no ICE, just a segfault.)
Comment #1 by braddr — 2007-06-15T15:31:41Z
A segv *is* an internal compiler error. I'm not inclined to add categories that are that subtly different.