diff options
| author | Thomas Schwinge <tschwinge@gnu.org> | 2012-08-07 23:25:26 +0200 |
|---|---|---|
| committer | Thomas Schwinge <tschwinge@gnu.org> | 2012-08-07 23:25:26 +0200 |
| commit | 2603401fa1f899a8ff60ec6a134d5bd511073a9d (patch) | |
| tree | ccac6e11638ddeee8da94055b53f4fdfde73aa5c /open_issues/strict_aliasing.mdwn | |
| parent | d72694b33a81919368365da2c35d5b4a264648e0 (diff) | |
IRC.
Diffstat (limited to 'open_issues/strict_aliasing.mdwn')
| -rw-r--r-- | open_issues/strict_aliasing.mdwn | 10 |
1 files changed, 10 insertions, 0 deletions
diff --git a/open_issues/strict_aliasing.mdwn b/open_issues/strict_aliasing.mdwn index 01019372..b7d39805 100644 --- a/open_issues/strict_aliasing.mdwn +++ b/open_issues/strict_aliasing.mdwn @@ -19,3 +19,13 @@ License|/fdl]]."]]"""]] instead? <braunr> pinotree: if we can rely on gcc for the warnings, yes <braunr> but i suspect there might be other silent issues in very old code + + +# IRC, freenode, #hurd, 2012-07-12 + + <braunr> btw, i'm building glibc right now, and i can see a few strict + aliasing warnings + <braunr> fixing them will allow us to avoid wasting time on very obscure + issues (if gcc catches them all) + <tschwinge> The strict aliasing things should be fixed, yes. Some might be + from MIG. |