Date: Fri, 9 Dec 2011 12:49:57 -0500 From: Arnaud Lacombe <lacombar@gmail.com> To: Rafal Jaworowski <raj@semihalf.com> Cc: freebsd-hackers@freebsd.org, Gleb Kurtsou <gleb.kurtsou@gmail.com>, Nathan Whitehorn <nwhitehorn@freebsd.org>, mdf@freebsd.org, Piotr Nowak <pn@semihalf.com> Subject: Re: gcc 4.2 miscompilation with -O2 -fno-omit-frame-pointer on amd64 Message-ID: <CACqU3MVO-oWso%2BF4G%2BRP4d%2By761=-Oz3COt2ubDogdBK834jEA@mail.gmail.com> In-Reply-To: <6D023449-EDEA-4B1C-975D-54AA2F4328CE@semihalf.com> References: <20111119100150.GA1560@reks> <CACqU3MXf%2BsbTpZMbqugmMKKb1BEbp6sNzeTkXfvnQtZ1E4ukEA@mail.gmail.com> <BA73AB23-650A-4241-BBAC-BA01BD372AA3@semihalf.com> <20111208090159.GA1924@cq1> <4EE0EB8C.7050800@freebsd.org> <6D023449-EDEA-4B1C-975D-54AA2F4328CE@semihalf.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi, On Fri, Dec 9, 2011 at 10:15 AM, Rafal Jaworowski <raj@semihalf.com> wrote: > > On 2011-12-08, at 17:53, Nathan Whitehorn wrote: > >> On 12/08/11 03:01, Piotr Nowak wrote: >>> We're working on PowerPC target using GCC 4.2.1 >>> and FreeBSD 6.1. It seems like we have similar >>> problem. In our case GCC sometimes very unfortunately >>> optimize code with -fno-omit-frame-pointer. >>> >>> Example shown below covers file sys/powerc/booke/pmap.c >>> and function pmap_kenter. If we disassemble kernel binary >>> we have: >>> >>> c019998c: =A0 4b ec 6a ed =A0 =A0 bl =A0 =A0 =A0c0060478<_mtx_unlock_sp= in_flags> >>> c0199990: =A0 81 61 00 00 =A0 =A0 lwz =A0 =A0 r11,0(r1) >>> c0199994: =A0 80 0b 00 04 =A0 =A0 lwz =A0 =A0 r0,4(r11) >>> c0199998: =A0 7d 61 5b 78 =A0 =A0 mr =A0 =A0 =A0r1,r11 >>> c019999c: =A0 82 ab ff d4 =A0 =A0 lwz =A0 =A0 r21,-44(r11) >>> c01999a0: =A0 7c 08 03 a6 =A0 =A0 mtlr =A0 =A0r0 >>> c01999a4: =A0 82 cb ff d8 =A0 =A0 lwz =A0 =A0 r22,-40(r11) >>> c01999a8: =A0 82 eb ff dc =A0 =A0 lwz =A0 =A0 r23,-36(r11) >>> c01999ac: =A0 83 0b ff e0 =A0 =A0 lwz =A0 =A0 r24,-32(r11) >>> c01999b0: =A0 83 2b ff e4 =A0 =A0 lwz =A0 =A0 r25,-28(r11) >>> c01999b4: =A0 83 4b ff e8 =A0 =A0 lwz =A0 =A0 r26,-24(r11) >>> c01999b8: =A0 83 6b ff ec =A0 =A0 lwz =A0 =A0 r27,-20(r11) >>> >>> As you can see stack pointer on R1 is being updated >>> before stashed data were pulled off stack. (mr r1,r11) >>> As a result of this we have chance to get crash when >>> any interrupt hit shortly after stack pointer update. >>> The interrupt prologue will override not yet pulled off >>> pmap_kenter function data. >>> >>> The problem occures only with -fno-omit-frame-pointer >>> and not every branch returns are beeing corrupted. >>> >>> Do you think this issue may be somehow related to yours? >>> Are there any patches/solutions to fix it? >> >> Should we turn off -fno-omit-frame-frame-pointer on PPC then? It's enabl= ed in default kernel builds. > > I think that's a good idea. Even though we have managed to trigger this o= nly in rare cases, the problem is real and the code generated is broken i.e= . leads to corruption and panics. > How can you make any conclusion without having seen a single line of code actually triggering the problem ? That sounds very irresponsible... - Arnaud
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CACqU3MVO-oWso%2BF4G%2BRP4d%2By761=-Oz3COt2ubDogdBK834jEA>