diff options
| author | Samuel Thibault <samuel.thibault@ens-lyon.org> | 2012-12-30 00:36:20 +0100 |
|---|---|---|
| committer | Samuel Thibault <samuel.thibault@ens-lyon.org> | 2012-12-30 00:36:20 +0100 |
| commit | e9235e964397bc2c5c6ca1858aba5c098b591660 (patch) | |
| tree | f105012a160e801e96ec81f2d26b447deb835d08 /open_issues/strict_aliasing.mdwn | |
| parent | d90af7499de9d0c58215691174826f956ff6612c (diff) | |
| parent | 55ffc6f5698b61c75260ff12b2591e3032b0651e (diff) | |
Merge branch 'master' of git.savannah.gnu.org:/srv/git/hurd/web
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. |