diff options
| author | Thomas Schwinge <tschwinge@gnu.org> | 2013-10-27 19:15:06 +0100 |
|---|---|---|
| committer | Thomas Schwinge <tschwinge@gnu.org> | 2013-10-27 19:15:06 +0100 |
| commit | 47e4d194dc36adfcfd2577fa4630c9fcded005d3 (patch) | |
| tree | d16ffd2eeb74d1977fb3e9744e4a38befedb4ddf /open_issues/strict_aliasing.mdwn | |
| parent | ca39ad0592e9b99dac9d99c68bb36ef1d27f72df (diff) | |
IRC.
Diffstat (limited to 'open_issues/strict_aliasing.mdwn')
| -rw-r--r-- | open_issues/strict_aliasing.mdwn | 15 |
1 files changed, 14 insertions, 1 deletions
diff --git a/open_issues/strict_aliasing.mdwn b/open_issues/strict_aliasing.mdwn index b7d39805..0e59f796 100644 --- a/open_issues/strict_aliasing.mdwn +++ b/open_issues/strict_aliasing.mdwn @@ -1,4 +1,4 @@ -[[!meta copyright="Copyright © 2012 Free Software Foundation, Inc."]] +[[!meta copyright="Copyright © 2012, 2013 Free Software Foundation, Inc."]] [[!meta license="""[[!toggle id="license" text="GFDL 1.2+"]][[!toggleable id="license" text="Permission is granted to copy, distribute and/or modify this @@ -29,3 +29,16 @@ License|/fdl]]."]]"""]] issues (if gcc catches them all) <tschwinge> The strict aliasing things should be fixed, yes. Some might be from MIG. + + +# IRC, freenode, #hurd, 2013-10-17 + + <braunr> we should build gnumach and the hurd with -fno-strict-aliasing + <pinotree> aren't the mig-generated stubs the only issues related to that? + <braunr> no + <teythoon> b/c we often have pointers of different type pointing to the + same address? for example code using libports? + <braunr> the old linux code, including pfinet, and even the hurd libraries, + use techniques that assume aliasing + <braunr> exactly + <teythoon> right, I agree |