From: "Carlos O'Donell Jr." <carlos@megatonmonkey.net>
To: Matthew Wilcox <willy@debian.org>, parisc-linux@lists.parisc-linux.org
Cc: baldric-exec@baldric.uwo.ca
Subject: Re: [parisc-linux] Glibc 2.2.4-2 No Optimizations = No Compliation
Date: Thu, 11 Oct 2001 09:59:13 -0400 [thread overview]
Message-ID: <20011011095913.A8106@megatonmonkey.net> (raw)
In-Reply-To: <20011011144718.A22924@parcelfarce.linux.theplanet.co.uk>; from willy@debian.org on Thu, Oct 11, 2001 at 02:47:18PM +0100
>
> I dunno... I oftn find optimised easier to read.
>
Really?
How about unrolled loops? ;)
In this case with GCC 3.0 being so fresh, there might
be some issues with -O2... so I'd like to see what
happend at -O0. I've patched, and I'm currently
recompiling with -O0... so we'll see.
>
> I don't know. But I guess glibc needs to inline something, and this doesn't
> happen below -O1.
>
True. But that really shouldn't make much difference since
AFAIK inlining doesn't happen until -O2, but config.h just says...
"You must have atleast -O1"
Those inlines, if they aren't there, would cause the build to fail...
and I still haven't seen any indication of this.
We shall see. If -O0 still segfaults, I'll trace that asm and
see what I can see... damn this all sounds so much like voodoo
magic.
c.
next prev parent reply other threads:[~2001-10-11 13:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-11 11:31 [parisc-linux] Glibc 2.2.4-2 No Optimizations = No Compliation Carlos O'Donell Jr.
2001-10-11 13:47 ` Matthew Wilcox
2001-10-11 13:59 ` Carlos O'Donell Jr. [this message]
2001-10-11 14:03 ` Matthew Wilcox
2001-10-11 14:19 ` Carlos O'Donell Jr.
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=20011011095913.A8106@megatonmonkey.net \
--to=carlos@megatonmonkey.net \
--cc=baldric-exec@baldric.uwo.ca \
--cc=parisc-linux@lists.parisc-linux.org \
--cc=willy@debian.org \
/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