From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jeffrey A Law To: Joe Buck Cc: torvalds@transmeta.com, craig@jcb-sc.com, mark@codesourcery.com, davem@redhat.com, chip@perlsupport.com, egcs@egcs.cygnus.com Subject: Re: Linux and aliasing? Date: Sun, 11 Jul 1999 10:55:00 -0000 Message-id: <2605.931715677@upchuck.cygnus.com> References: <199906041728.KAA19685@atrus.synopsys.com> X-SW-Source: 1999-07/msg00320.html In message <199906041728.KAA19685@atrus.synopsys.com>you write: > > > Either > > > 1. Leave it as it is (the Linux kernel will need -fno-strict-aliasing > ). > > This is my strong preference. > > In that case, then all release announcements and NEWS should prominently > mention the effect of this new optimization and the -fno-strict-aliasing > flag, so that everyone has fair warning. We've got preliminary entry in the FAQ. That entry is also referenced by the prototype gcc-2.95 features page as well as the prototype gcc-2.95 caveats page. I hope to improve the faq entry before the actual release. In particular we want to include a better explanation of the generic problem (along with a code sample?) as well as various options one could use to fix the code. Then we just mention the Linux kernel as an example of a package which is known to have this particular problem. This is basically what we did with the asm clobbers information. We've got a generic entry which describes the problem and it references a Linux kernel specific entry. jeff which show problem > > From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jeffrey A Law To: Joe Buck Cc: torvalds@transmeta.com, craig@jcb-sc.com, mark@codesourcery.com, davem@redhat.com, chip@perlsupport.com, egcs@egcs.cygnus.com Subject: Re: Linux and aliasing? Date: Sat, 31 Jul 1999 23:33:00 -0000 Message-ID: <2605.931715677@upchuck.cygnus.com> References: <199906041728.KAA19685@atrus.synopsys.com> X-SW-Source: 1999-07n/msg00320.html Message-ID: <19990731233300.TVBqFNxaMp7tuyLb9un19KPsMk0ItsEQq_BRAm8Jh8Q@z> In message <199906041728.KAA19685@atrus.synopsys.com>you write: > > > Either > > > 1. Leave it as it is (the Linux kernel will need -fno-strict-aliasing > ). > > This is my strong preference. > > In that case, then all release announcements and NEWS should prominently > mention the effect of this new optimization and the -fno-strict-aliasing > flag, so that everyone has fair warning. We've got preliminary entry in the FAQ. That entry is also referenced by the prototype gcc-2.95 features page as well as the prototype gcc-2.95 caveats page. I hope to improve the faq entry before the actual release. In particular we want to include a better explanation of the generic problem (along with a code sample?) as well as various options one could use to fix the code. Then we just mention the Linux kernel as an example of a package which is known to have this particular problem. This is basically what we did with the asm clobbers information. We've got a generic entry which describes the problem and it references a Linux kernel specific entry. jeff which show problem > >