From: Ralf Baechle <ralf@linux-mips.org>
To: Atsushi Nemoto <anemo@mba.ocn.ne.jp>
Cc: linux-mips@linux-mips.org
Subject: Re: 2.4 pci_dma_sync_sg fix
Date: Thu, 1 Jul 2004 15:59:19 +0200 [thread overview]
Message-ID: <20040701135919.GA6906@linux-mips.org> (raw)
In-Reply-To: <20040701.224535.71082878.anemo@mba.ocn.ne.jp>
On Thu, Jul 01, 2004 at 10:45:35PM +0900, Atsushi Nemoto wrote:
> >>>>> On Thu, 1 Jul 2004 15:22:40 +0200, Ralf Baechle <ralf@linux-mips.org> said:
>
> ralf> Leave the #ifdef stuff there - or otherwise gcc might optimize
> ralf> this into empty loops ...
>
> The loop contains paranoid out_of_line_bug, so it never be optimized
> to empty.
Indeed and I think that's a bit of overkill. I've never seen these
assertions catch any bugs - and 2.4 isn't exactly new anymore. Anyway,
even if the loop was empty gcc would not eleminate it.
Ralf
next prev parent reply other threads:[~2004-07-01 16:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-01 13:21 2.4 pci_dma_sync_sg fix Atsushi Nemoto
2004-07-01 13:22 ` Ralf Baechle
2004-07-01 13:45 ` Atsushi Nemoto
2004-07-01 13:59 ` Ralf Baechle [this message]
2004-07-03 12:44 ` Atsushi Nemoto
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=20040701135919.GA6906@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=anemo@mba.ocn.ne.jp \
--cc=linux-mips@linux-mips.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