linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Brian Gerst <bgerst@didntduck.org>
Cc: Luciano Miguel Ferreira Rocha <luciano@lsd.di.uminho.pt>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Interrupt doesn't make it to the 8259 on a ASUS P4PE mobo
Date: 15 Jul 2003 19:44:26 +0100	[thread overview]
Message-ID: <1058294665.3845.61.camel@dhcp22.swansea.linux.org.uk> (raw)
In-Reply-To: <3F1446E9.8040409@didntduck.org>

On Maw, 2003-07-15 at 19:24, Brian Gerst wrote:
> Luciano Miguel Ferreira Rocha wrote:
> > On Tue, Jul 15, 2003 at 01:06:19PM -0400, Brian Gerst wrote:
> > 
> >>Use HZ/2 instead.  GCC doesn't optimize floating point constants to the 
> >>same degree it does integers, because it doesn't know what mode 
> >>(rounding, precision) the FPU is in.
> > 
> > 
> > Isn't (HZ >> 1) better?
> 
> Same thing.  GCC knows that division by a power of 2 is just a shift.

Only for unsigned

  reply	other threads:[~2003-07-15 18:32 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <m3el0stw23.fsf@averell.firstfloor.org>
2003-07-15 16:14 ` Interrupt doesn't make it to the 8259 on a ASUS P4PE mobo Kathy Frazier
2003-07-15 15:31   ` Richard B. Johnson
2003-07-15 15:58     ` SCSI ATA driver in 2.4.22 ? Jeff Mock
2003-07-15 16:14       ` Jeff Garzik
2003-07-15 17:06   ` Interrupt doesn't make it to the 8259 on a ASUS P4PE mobo Brian Gerst
2003-07-15 17:43     ` Jamie Lokier
2003-07-15 17:59     ` Luciano Miguel Ferreira Rocha
2003-07-15 18:24       ` Brian Gerst
2003-07-15 18:44         ` Alan Cox [this message]
2003-07-15 19:44           ` Jamie Lokier
2003-07-20 21:04           ` Riley Williams
2003-07-20 22:25             ` Jeremy Fitzhardinge
     [not found] <Pine.LNX.4.53.0307141833190.4354@chaos>
2003-07-15 16:52 ` Kathy Frazier
2003-07-14 21:35 Kathy Frazier

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=1058294665.3845.61.camel@dhcp22.swansea.linux.org.uk \
    --to=alan@lxorguk.ukuu.org.uk \
    --cc=bgerst@didntduck.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luciano@lsd.di.uminho.pt \
    /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).