From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 In-Reply-To: <6e175dbec62e688b0023a491aaf20591@swcp.com> References: <6da24933b67d68d259a2be1d08fe1a27@terzarima.net> <4ac0a1471e109a787e173b6267e38856@kw.quanstro.net> <6e175dbec62e688b0023a491aaf20591@swcp.com> Date: Sat, 29 May 2010 05:13:55 +0000 Message-ID: From: ron minnich To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Subject: Re: [9fans] crashing 9vx Topicbox-Message-UUID: 2d1d6ca6-ead6-11e9-9d60-3106f5b1d025 On Sat, May 29, 2010 at 4:05 AM, EBo wrote: > =A0gcc -fno-inline -c -g -O3 -MD -std=3Dgnu99 -O2 -march=3Di486 -pipe > > and > > =A0gcc -m32 -c -nostdinc --g -O3 -MD -std=3Dgnu99 -O2 -march=3Di486 -pipe > -fno-stack-protector -m80387 -mfp-ret-in-387 The stack protector code came in to some distros (e.g. ubuntu) and it causes major trouble (for coreboot among other things) if you do things slightly out of the standard. You need -fno-stack-protector I would assume with vx32. > Ron, did you use any optimization or taken it out completely. =A0Also, ar= e > you going to add this patch to your repository, or should we handle it on > our end? it's now commited to my vx32 tree. Fast is good, but lack of blowups is bet= ter. ron