diff options
| author | Thomas Schwinge <thomas@codesourcery.com> | 2012-12-11 11:04:11 +0100 |
|---|---|---|
| committer | Thomas Schwinge <thomas@codesourcery.com> | 2012-12-11 11:04:11 +0100 |
| commit | 1c36eb6c025084af76c5b930ca4adc5953560fd7 (patch) | |
| tree | 8ac3bcf1f785997cce064c65dcd729be4c5dcb0b /open_issues/strict_aliasing.mdwn | |
| parent | a0290d994030cd14bdccbb97d2a2c022d1d2428c (diff) | |
| parent | bcfc058a332da0a2bd2e09e13619be3e2eb803a7 (diff) | |
Merge remote-tracking branch 'fp/master'
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. |