All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan-Benedict Glaw <jbglaw@lug-owl.de>
To: linux-kernel@vger.kernel.org
Subject: Re: FEATURE REQUEST: Specific Processor Optimizations on x86 Architecture
Date: Thu, 23 Oct 2003 11:35:05 +0200	[thread overview]
Message-ID: <20031023093504.GP20846@lug-owl.de> (raw)
In-Reply-To: <200310222135.22968.theman@josephdwagner.info>

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

On Wed, 2003-10-22 21:35:22 +0600, Joseph D. Wagner <theman@josephdwagner.info>
wrote in message <200310222135.22968.theman@josephdwagner.info>:

> I respectivly disagree with those reasons.  -march is gcc flag.  If it 
> creates any instability (doubtful), it's really a gcc problem.  Throwing it 
> in will light a fire under their @$$ to get their act together.

It *may* happen that some things work a bit differently. This needn't be
an exact compiler error. It may be a Linux kernel source error. However,
these things are quite subtle so it might break things and you only see
it after a month or two, when you on-HDD data is already gone...

Changes like that need good tests and can't be done in a 2.4.x kernel
becase it may harm people's data or stability. These changes need to be
done in development kernels, hopefully when they start off, not when
they settle down to become the next stable release, though...

MfG, JBG

-- 
   Jan-Benedict Glaw       jbglaw@lug-owl.de    . +49-172-7608481
   "Eine Freie Meinung in  einem Freien Kopf    | Gegen Zensur | Gegen Krieg
    fuer einen Freien Staat voll Freier Bürger" | im Internet! |   im Irak!
   ret = do_actions((curr | FREE_SPEECH) & ~(NEW_COPYRIGHT_LAW | DRM | TCPA));

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

  parent reply	other threads:[~2003-10-23  9:35 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-22 12:55 FEATURE REQUEST: Specific Processor Optimizations on x86 Architecture Joseph D. Wagner
2003-10-23  0:12 ` Måns Rullgård
2003-10-22 13:26   ` Joseph D. Wagner
2003-10-23  0:37   ` Michael Rozhavsky
2003-10-23  0:15 ` Dave Jones
2003-10-22 13:47   ` Joseph D. Wagner
2003-10-23  1:02     ` Rik van Riel
2003-10-23  1:14       ` Joseph D. Wagner
2003-10-23  1:18         ` Rik van Riel
2003-10-23  9:26         ` Jan-Benedict Glaw
2003-10-23  9:35         ` Måns Rullgård
2003-10-23  1:06     ` Tim Hockin
2003-10-22 15:40       ` Joseph D. Wagner
2003-10-23 14:57         ` Rik van Riel
2003-10-23  1:23     ` Dave Jones
2003-10-22 15:35       ` Joseph D. Wagner
2003-10-23  2:52         ` William Lee Irwin III
2003-10-23  9:35         ` Jan-Benedict Glaw [this message]
2003-10-23 13:40         ` Jesse Pollard
2003-10-23 14:57     ` Charles Cazabon
2003-10-23 15:34 ` David Zaffiro
2003-10-23 17:26 ` Rob
2003-10-23 23:05 ` J.A. Magallon
2003-10-23 23:24   ` Nick Piggin
     [not found]   ` <200310241301.41230.ioe-lkml@rameria.de>
2003-10-27 15:20     ` J.A. Magallon
2003-10-27 20:52       ` Zwane Mwaikambo
     [not found] <JB3R.23s.23@gated-at.bofh.it>
     [not found] ` <JBn4.2xt.19@gated-at.bofh.it>
     [not found]   ` <JBPW.36x.3@gated-at.bofh.it>
2003-10-23  8:32     ` Ihar 'Philips' Filipau
2003-10-23  8:37     ` Ihar 'Philips' Filipau
     [not found] ` <JWKQ.7nS.15@gated-at.bofh.it>
     [not found]   ` <LhtX.bs.15@gated-at.bofh.it>
     [not found]     ` <LhtX.bs.13@gated-at.bofh.it>
2003-10-27 18:33       ` Andi Kleen
2003-10-27 21:05         ` Zwane Mwaikambo
     [not found] <JB3R.23s.23@gated-at.bofh.it.suse.lists.linux.kernel>
     [not found] ` <JWKQ.7nS.15@gated-at.bofh.it.suse.lists.linux.kernel>
     [not found]   ` <LhtX.bs.15@gated-at.bofh.it.suse.lists.linux.kernel>
     [not found]     ` <LhtX.bs.13@gated-at.bofh.it.suse.lists.linux.kernel>
     [not found]       ` <m3k76qsf8i.fsf@averell.firstfloor.org.suse.lists.linux.kernel>
     [not found]         ` <Pine.LNX.4.53.0310271603580.21953@montezuma.fsmlabs.com.suse.lists.linux.kernel>
2003-10-27 21:15           ` Andi Kleen
2003-11-18 14:28             ` Zwane Mwaikambo

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=20031023093504.GP20846@lug-owl.de \
    --to=jbglaw@lug-owl.de \
    --cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.