Re: GCC-4 problems

[Paul M. <pau...@re...>]

On Sat, Jul 07, 2007 at 02:26:56PM +0200, Manuel Lauss wrote:
> Manuel Lauss wrote:
> > Paul Mundt wrote:
> >> On Mon, Mar 19, 2007 at 09:27:57AM +0100, Manuel Lauss wrote:
> >>> Also, these exports need to be removed from sh_ksyms.c, they give
> >>> "undefined reference" errors:
> >>> __sdivsi3_i4i __udiv_qrnnd_16 __udivsi3_i4i
> >>>
> >> Ok, so removing these seems to be have created fallout all over the
> >> place. Apparently it's just your GCC4 that seems to have problems with
> >> these symbols, whereas the other ones really seem to want them. It looks
> >> like we're going to have to narrow it down to the exact release in which
> >> they vanished (I would guess 4.1.2, since 4.1.1 still wants them).
> >>
> >> akpm also suggests he has a 3.4.5 toolchain that needs these, which is
> >> also very unusual. Do you have a tarball of your compiler somewhere so
> >> it's easier to debug?
> > 
> > __udiv_qrnnd_16 was introduced by this GCC PR:
> > http://gcc.gnu.org/bugzilla/show_bug.cgi?id=28014
> > 
> > I'll test 4.2.0 next.
> 
> Confirmed, 4.2.0 does not complain about undefined references.
> 
> So maybe those defines should be made dependent on gcc >= 4.2 ?
> Although that wouldn't solve akpm's Problem with 3.4..
> 
Well, these symbols also exist in the ST compiler, which is on 4.1.1. So
we probably have to special case for that.

It looks like we're just going to have to include these symbols in the
kernel directly in arch/sh/lib if we want to support this generically.
I'll hack something up this week.