public inbox for linuxppc-dev@ozlabs.org 
 help / color / mirror / Atom feed
From: Franz Sirl <Franz.Sirl-kernel@lauterbach•com>
To: Corey Minyard <minyard@acm•org>
Cc: linuxppc-dev@lists•linuxppc.org
Subject: Re: Changes to PPC Linux required for GCC 3.1
Date: Wed, 5 Dec 2001 21:51:02 +0100	[thread overview]
Message-ID: <200112052146.16467@enzo.bigblue.local> (raw)
In-Reply-To: <3C0E48D2.6000409@acm.org>


On Wednesday 05 December 2001 17:18, Corey Minyard wrote:
> Franz Sirl wrote:
> > Ah, I see, I only saw this problem in aty128fb. I'll add the fix to
> > the linuxconsole CVS for 2.5.x.
>
> What about 2.4?  I'm sure people will want to compile 2.4 with gcc 3.x.

That has to go thru the usual channels.

> >> * In include/linux/sunrpc/clnt.h, I removed a bogus function declaration
> >> which was messing up inlining.
> >
> > I guess this is 3.1 specific? I don't remember problems with 3.0.x.
>
> Probably.  I've seen some other problems with GCC being fairly picky
> about declarations, and I think it's fairly new.  But the declaration
> both wrong and unnecessary.

Ah yes, I browsed this discussion on the lists.

> > What about the FAT filesystem? Is gcc-3.1 now able to correctly
> > optimize the 64bit signed divide by const into a ASHIFT+fixup?
>
> Nope.  I was going to ask about that one.  Do you have a GCC PR on this?

Nope, probably I should add one, cause I don't have time to continue with a
divdi3_32 pattern anytime soon :-(.

Franz.

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

  parent reply	other threads:[~2001-12-05 20:51 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-04 16:13 Changes to PPC Linux required for GCC 3.1 Corey Minyard
2001-12-04 16:16 ` David Edelsohn
2001-12-04 16:39   ` Corey Minyard
2001-12-05 12:55 ` Franz Sirl
2001-12-05 16:18   ` Corey Minyard
2001-12-05 17:37     ` Tom Rini
2001-12-05 17:50       ` Benjamin Herrenschmidt
2001-12-05 19:45         ` Tom Rini
2001-12-05 20:30           ` Franz Sirl
2001-12-07 13:01             ` Gabriel Paubert
2001-12-07 20:57               ` AltiVec register ptrace support Kumar Gala
2001-12-07 22:23                 ` Kevin Buettner
2001-12-07 22:34                   ` Daniel Jacobowitz
2001-12-14 18:52                     ` Kumar Gala
2001-12-14 19:16                       ` Jason R Thorpe
2001-12-15  2:08                       ` Andrew Cagney
2001-12-15 17:44                         ` Kumar Gala
2001-12-16 21:11                         ` Paul Mackerras
2002-01-10 18:58                           ` Kumar Gala
2001-12-05 21:59         ` Changes to PPC Linux required for GCC 3.1 Paul Mackerras
2001-12-05 20:17       ` Daniel Jacobowitz
2001-12-05 20:20         ` David Edelsohn
2001-12-05 20:30         ` Franz Sirl
2001-12-06  0:59       ` Corey Minyard
2001-12-06  3:38         ` Tom Rini
2001-12-07  5:22           ` Corey Minyard
2001-12-05 20:51     ` Franz Sirl [this message]
2001-12-06  1:41       ` Corey Minyard
  -- strict thread matches above, loose matches on Subject: below --
2001-03-06 16:03 who loads argc in elf binary??????? Alexandre Nikolaev
2001-03-07 19:10 ` Daniel Jacobowitz
2001-03-07 19:15   ` David Edelsohn

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=200112052146.16467@enzo.bigblue.local \
    --to=franz.sirl-kernel@lauterbach$(echo .)com \
    --cc=linuxppc-dev@lists$(echo .)linuxppc.org \
    --cc=minyard@acm$(echo .)org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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