public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Spider <spider@gentoo.org>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] Proposition for stage3.
Date: Tue, 18 Jun 2002 23:38:19 +0200	[thread overview]
Message-ID: <20020618233819.6c1705f3.spider@gentoo.org> (raw)
In-Reply-To: <20020618154800.41276e24.rufiao@gmx.net>

[-- Attachment #1: Type: text/plain, Size: 1569 bytes --]

begin  quote
On Tue, 18 Jun 2002 15:48:00 -0300
Rufiao <rufiao@gmx.net> wrote:

> 
> I haven't build a whole system using that yet. Any packages break 
> specifically because of this flag?
> 
> Per Wigren [Tue 18-Jun-2002 18:41 GMT+0200]:
> > -fomit-frame-pointer often gives a noticable speedup also...



I will personally slay the person to include this in the default system,
as -any- bug found at a higher level in the chain will be rendered
completely undebuggable  if glibc or other library that it links uses
this, The initial speedup is trivial for things such as the basesystem,
and to simply ignore all bugreports from a person who uses it is quite a
valid proposition as far as I'm concerned. 

Why the strong feelings about it? bugreports are quite vital to our QA
and future survival, and to our users if they ever want to try anything
even remotely unstable, or development (face it, quite a few do), and
the amount of trouble this flag generates further down the line is
immense.

Yes, you can leave it as a suggestion if you wish, though it should be
noted that "this will break all debugging and render all bugreports
useless, as well as it may introduce odd crashes which will not be
traceable" , But it should -not- be thought of as an default
alternative. 

Better for defaults would be -fno-exceptions  for C++ and C code, 
although this also breaks code, but more noticable in most cases.

//Spider


--
begin  .signature
This is a .signature virus! Please copy me into your .signature!
See Microsoft KB Article Q265230 for more information.
end

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

      parent reply	other threads:[~2002-06-18 21:38 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-18 15:52 [gentoo-dev] Proposition for stage3 Dan Naumov
2002-06-18 16:22 ` Bart Verwilst
2002-06-18 16:41   ` Per Wigren
2002-06-18 18:48     ` Rufiao
2002-06-18 19:27       ` Per Wigren
2002-06-18 20:13       ` Prashanth Aditya Susarla
2002-06-18 21:38       ` Spider [this message]

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=20020618233819.6c1705f3.spider@gentoo.org \
    --to=spider@gentoo.org \
    --cc=gentoo-dev@gentoo.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