summaryrefslogtreecommitdiff
path: root/open_issues/strict_aliasing.mdwn
diff options
context:
space:
mode:
authorhttps://me.yahoo.com/a/g3Ccalpj0NhN566pHbUl6i9QF0QEkrhlfPM-#b1c14 <diana@web>2015-02-16 20:08:03 +0100
committerGNU Hurd web pages engine <web-hurd@gnu.org>2015-02-16 20:08:03 +0100
commit95878586ec7611791f4001a4ee17abf943fae3c1 (patch)
tree847cf658ab3c3208a296202194b16a6550b243cf /open_issues/strict_aliasing.mdwn
parent8063426bf7848411b0ef3626d57be8cb4826715e (diff)
rename open_issues.mdwn to service_solahart_jakarta_selatan__082122541663.mdwn
Diffstat (limited to 'open_issues/strict_aliasing.mdwn')
-rw-r--r--open_issues/strict_aliasing.mdwn44
1 files changed, 0 insertions, 44 deletions
diff --git a/open_issues/strict_aliasing.mdwn b/open_issues/strict_aliasing.mdwn
deleted file mode 100644
index 0e59f796..00000000
--- a/open_issues/strict_aliasing.mdwn
+++ /dev/null
@@ -1,44 +0,0 @@
-[[!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
-document under the terms of the GNU Free Documentation License, Version 1.2 or
-any later version published by the Free Software Foundation; with no Invariant
-Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license
-is included in the section entitled [[GNU Free Documentation
-License|/fdl]]."]]"""]]
-
-[[!tag open_issue_glibc open_issue_gnumach open_issue_hurd open_issue_mig]]
-
-
-# IRC, freenode, #hurd, 2012-07-04
-
- <braunr> we should perhaps build the hurd with -fno-strict-aliasing,
- considering the number of warnings i can see during the build :/
- <pinotree> braunr: wouldn't be better to "just" fix the mig-generated stubs
- 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.
-
-
-# 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