Bug 82681
Summary: | gcc warning on possible code problem is issuedinconstently | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | Michael Marxmeier <mike> |
Component: | gcc3 | Assignee: | Jakub Jelinek <jakub> |
Status: | CLOSED NOTABUG | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 8.0 | ||
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i386 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2003-01-24 20:54:11 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Michael Marxmeier
2003-01-24 20:51:27 UTC
Your code triggers undefined behaviour, and as such gcc can do anything it wants with it. As i wrote above, it might be undefined behavior and i'm not arguing that (it's just likely to break lots of existing code). However (IMHO) gcc should issue the warning consistently if -Wall is present. I've seen a number of cases where the warning was not issued, with -O used. I'm not pushing this but please consider to reopen the bug for the issue #2 (warning) - i've updated the subject accordingly. |