From 8cee055ec4fac00e59f19620ab06e2b30dccee3c Mon Sep 17 00:00:00 2001 From: Thomas Schwinge Date: Wed, 11 Jul 2012 22:39:59 +0200 Subject: IRC. --- open_issues/strict_aliasing.mdwn | 21 +++++++++++++++++++++ 1 file changed, 21 insertions(+) create mode 100644 open_issues/strict_aliasing.mdwn (limited to 'open_issues/strict_aliasing.mdwn') diff --git a/open_issues/strict_aliasing.mdwn b/open_issues/strict_aliasing.mdwn new file mode 100644 index 00000000..01019372 --- /dev/null +++ b/open_issues/strict_aliasing.mdwn @@ -0,0 +1,21 @@ +[[!meta copyright="Copyright © 2012 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 + + we should perhaps build the hurd with -fno-strict-aliasing, + considering the number of warnings i can see during the build :/ + braunr: wouldn't be better to "just" fix the mig-generated stubs + instead? + pinotree: if we can rely on gcc for the warnings, yes + but i suspect there might be other silent issues in very old code -- cgit v1.2.3