mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: devik <devik@cdi.cz>
To: Robert Love <rml@tech9.net>
Cc: Chris Meadors <clubneon@hereintown.net>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: gcc 3.0.2/kernel details (-O issue)
Date: Thu, 20 Dec 2001 11:30:21 +0100 (CET)	[thread overview]
Message-ID: <Pine.LNX.4.33.0112201115030.626-100000@devix> (raw)
In-Reply-To: <1008792213.806.36.camel@phantasy>

> Well, you certainly won't get errors, because compiler optimizations
> shouldn't change expected syntax.

not always true, inb() doesn't compile without -O for example.

> -O2 is the standard optimization level for the kernel; everything is
> compiled via it.  When developers test their code, nuances that the
> optimization introduce are accepted.  Removing the optimization may
> break those expectations.  Thus the kernel requires it.

I'm quite comfortable with the requirement, only I can't imagine
code which depends on -O and -O2 difference. Inline assembly is
handled by compiler so it should not break things ..
Maybe externaly linked assembly code ? But optimization level should
not change register usage in calling convention ..
Please can you give me example which kind of code breaks those
expectations ?

Thanks, Martin


  parent reply	other threads:[~2001-12-20 10:34 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-19 18:55 devik
2001-12-19 19:49 ` Chris Meadors
2001-12-19 19:39   ` Martin Devera
2001-12-19 20:03     ` Robert Love
2001-12-20  0:10       ` Erik Mouw
2001-12-20  3:39         ` H. Peter Anvin
2001-12-20  9:22           ` J.A. Magallon
2001-12-20 12:03             ` H. Peter Anvin
2001-12-20 10:30       ` devik [this message]
2001-12-22 20:54       ` Pavel Machek
2001-12-22 23:35         ` devik
2001-12-22 23:54         ` J.A. Magallon

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=Pine.LNX.4.33.0112201115030.626-100000@devix \
    --to=devik@cdi.cz \
    --cc=clubneon@hereintown.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rml@tech9.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

all inboxes | Powered by JetHome®