public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Franz Sirl <Franz.Sirl-kernel@lauterbach.com>
To: Linus Torvalds <torvalds@transmeta.com>
Cc: Richard Henderson <rth@redhat.com>, <gcc@gcc.gnu.org>
Subject: Re: Optimizations on long long multiply/divide on PowerPC32  don't work
Date: Mon, 10 Dec 2001 10:59:00 -0000	[thread overview]
Message-ID: <200112101938.4189@enzo.bigblue.local> (raw)
In-Reply-To: <Pine.LNX.4.33.0112100904150.14166-100000@penguin.transmeta.com>

On Monday 10 December 2001 18:08, Linus Torvalds wrote:
> On Mon, 10 Dec 2001, Franz Sirl wrote:
> > Ah, now that is nice, I always wondered which codepath produced the
> > signeddivide64-by-exactlog2constant to shift conversion on x86, but
> > couldn't find anything in i386.md :-(. I'll try that one on 3.0.3pre and
> > see if the FAT FS compiles again (I wonder if my ashrdi3_nopower pattern
> > will get used then?).
>
> Which part of FAT-FS actually tries to do a signed division?

It's this code fragment:

        inode->i_blocks = ((inode->i_size + inode->i_blksize - 1)
                           & ~(inode->i_blksize - 1)) / 512;

that is in inode.c/fat_read_root() and fat_fill_inode(). It's inode->i_size 
that is of type loff_t here.

> I have a VERY strong suspicion that any filesystem that wants to divide by
> 512 is really just getting a sector number, and the division should not be
> signed in the first place.

It calculates the number of blocks here, so the rounding up might be wanted...

> > Despite the missing GCC optimization, I always wondered if the FAT FS
> > really relies the roundup happening with a signed divide, or if we could
> > simply replace the "/512" with ">>9" without any ill effects? At least I
> > couldn't find anything documented in the code...
>
> It's almost certainly a "loff_t", and we should always have generated
> -EINVAL for negative offsets, so it's pretty much guaranteed to be
> positive modulo any bugs.
>
> Of course, with fatfs, who knows..

Hehe, yeah, exactly :-). Anyway, Richard's patch works fine and gcc3 now is 
able to optimize the divdi3 call away.

Franz.

  reply	other threads:[~2001-12-10 18:49 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-07 16:08 Corey Minyard
2001-12-07 17:08 ` Richard Henderson
2001-12-07 17:40   ` Corey Minyard
2001-12-09 23:29   ` Linus Torvalds
2001-12-10  1:15     ` Richard Henderson
2001-12-10  1:24       ` Richard Henderson
2001-12-10  2:40         ` Franz Sirl
2001-12-10  9:21           ` Linus Torvalds
2001-12-10 10:59             ` Franz Sirl [this message]
2001-12-10 11:11               ` Linus Torvalds
2001-12-10 11:31               ` Gabriel Paubert
2001-12-10 17:58                 ` Richard Henderson
2002-01-22  8:51         ` Franz Sirl
2002-01-22 12:04           ` Richard Henderson
2002-01-23  7:24             ` Gerald Pfeifer
2002-02-03 10:44               ` Franz Sirl
2001-12-10  9:15       ` Linus Torvalds
2001-12-10 13:03         ` Richard Henderson
2001-12-10 13:59           ` Linus Torvalds
2001-12-10  9:09     ` Paul Koning
2001-12-10 10:23       ` Linus Torvalds
2001-12-10 11:35         ` Optimizations on long long multiply/divide on PowerPC32 don't Joe Buck
2001-12-10 13:49           ` guerby
2001-12-10 14:08             ` Arnaud Charlet
2001-12-10 14:31               ` guerby
2001-12-10  9:09 ` Optimizations on long long multiply/divide on PowerPC32 don't work Christoph Hellwig
2001-12-07 18:28 mike stump

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=200112101938.4189@enzo.bigblue.local \
    --to=franz.sirl-kernel@lauterbach.com \
    --cc=gcc@gcc.gnu.org \
    --cc=rth@redhat.com \
    --cc=torvalds@transmeta.com \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).