From: EBo <ebo@sandien.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] crashing 9vx
Date: Fri, 28 May 2010 22:05:32 -0600 [thread overview]
Message-ID: <6e175dbec62e688b0023a491aaf20591@swcp.com> (raw)
In-Reply-To: <AANLkTil3is6tOfzMJg6Z03eYTZgnUBzBz9F8U4HSWw3C@mail.gmail.com>
On Sat, 29 May 2010 03:39:46 +0000, ron minnich <rminnich@gmail.com>
wrote:
> OK, somebody sent a hint that it might make sense to take the -O3 out
> of the make flags. Done.
>
> Result: I can now get through this command:
> hget -v
> http://plan9.bell-labs.com/plan9/download/plan9.iso.bz2>/tmp/iso.bz2
> |[2]aux/statusbar plan9.iso
>
> without an explosion.
Interesting. I had not noticed that 9vx was building on my machines with:
gcc -fno-inline -c -g -O3 -MD -std=gnu99 -O2 -march=i486 -pipe
and
gcc -m32 -c -nostdinc --g -O3 -MD -std=gnu99 -O2 -march=i486 -pipe
-fno-stack-protector -m80387 -mfp-ret-in-387
in other places. I would have removed -O3 if I had noticed it before.
I'm curious why the "-fno-stack-protector -m80387 -mfp-ret-in-387" was
required?
Ron, did you use any optimization or taken it out completely. Also, are
you going to add this patch to your repository, or should we handle it on
our end?
EBo --
next prev parent reply other threads:[~2010-05-29 4:05 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-28 4:10 ron minnich
2010-05-28 6:40 ` Philippe Anel
2010-05-28 8:13 ` Philippe Anel
2010-05-28 8:24 ` Philippe Anel
2010-05-28 15:10 ` ron minnich
2010-05-28 15:15 ` Philippe Anel
2010-05-28 15:24 ` ron minnich
2010-05-28 18:36 ` Charles Forsyth
2010-05-28 19:31 ` Philippe Anel
2010-05-28 20:46 ` ron minnich
2010-05-28 21:00 ` erik quanstrom
2010-05-29 3:39 ` ron minnich
2010-05-29 4:05 ` EBo [this message]
2010-05-29 5:13 ` ron minnich
2010-05-29 5:45 ` EBo
2010-05-29 4:09 ` erik quanstrom
2010-05-29 5:10 ` ron minnich
2010-05-30 14:46 ` Brian L. Stuart
2010-05-30 15:52 ` ron minnich
2010-05-30 15:59 ` Philippe Anel
2010-05-30 16:30 ` erik quanstrom
2010-05-31 1:33 ` Brian L. Stuart
2010-05-30 17:08 ` Bakul Shah
2010-05-31 1:14 ` Brian L. Stuart
2010-05-31 2:01 ` ron minnich
2010-05-31 16:32 ` ron minnich
2010-05-31 17:48 ` jake
2010-05-31 18:16 ` EBo
2010-05-31 20:46 ` Jorden M
2010-06-01 11:14 ` Charles Forsyth
2010-06-02 16:40 ` ron minnich
2010-05-29 5:47 ` EBo
2010-10-28 14:00 yy
2010-10-28 14:47 ` Lucio De Re
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=6e175dbec62e688b0023a491aaf20591@swcp.com \
--to=ebo@sandien.com \
--cc=9fans@9fans.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).