Edit - Software Engineering Stack Exchange

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

Rev

1

You're lucky. My average is about 1 really bad bug a month, and minor borderline issues are a way much more often. And the higher optimisation level you're using, the higher are compiler error chances. If you're trying to use -O3 and LTO, you'd be very lucky not to find a couple of them in no time. And I only count here the bugs in release versions - as a compilers developer, I'm facing much much more of problems of that kind in my work, but that does not count. I just know how easy it is to screw up a compiler.

SK-logic
– SK-logic

2011-09-26 10:00:22 +00:00
Commented Sep 26, 2011 at 10:00
2

25 years and I also have seen very many. The compilers are getting worse every year.

old_timer
– old_timer

2012-01-14 05:57:26 +00:00
Commented Jan 14, 2012 at 5:57

Add a comment |

Correct minor typos or mistakes
Clarify meaning without changing it
Add related resources or links
Always respect the author’s intent
Don’t use edits to reply to the author

create code fences with backticks ` or tildes ~
```
like so
```
add language identifier to highlight code
```python
def function(foo):
print(foo)
```
put returns between paragraphs
for linebreak add 2 spaces at end
_italic_ or **bold**
indent code by 4 spaces
backtick escapes `like _so_`
quote by placing > at start of line
to make links (use https whenever possible)

<https://example.com>

[example](https://example.com)

<a href="https://example.com">example</a>

formatting help »
answering help »