parisc: Kconfig: use 'PA8X00' as the default choise instead of 'PA7000'

PATCH In review Chen Gang 5 participants 13 messages Jul 24, 2013 – Jul 30, 2013 PA-RISC architecture

lore

Share & tools

lore

Chen Gang

author

2013-07-24 08:12 UTC #0 lore raw

PATCH 1/1 parisc: Kconfig: use 'PA8X00' as the default choise instead of 'PA7000'

=46or server, 64-bit kernel is widely used and '64BIT' have been alread= y
as the default option of a server.

So better to use 64-bit kernel as default choise instead of 32-bit kernel.

Or when use cross-compiler 'hppa64-linux-gnu-gcc' with allmodconfig, it will report BUILD_BUG_ON:

arch/parisc/mm/init.c: In function =91mem_init=92:
arch/parisc/mm/init.c:581:2: error: call to =91__compiletime_assert_5=
81=92 declared with attribute error: BUILD_BUG_ON failed: PTE_ENTRY_SIZ= E !=3D sizeof(pte_t)

Signed-off-by Chen Gang <[email protected]>

---
 arch/parisc/Kconfig |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)

arch/parisc/Kconfig +0 -0

index aa399a5..37bdecf 100644
@@ -111,7 +111,7 @@ menu "Processor type and features"

=20
choice
prompt "Processor type"
- default PA7000
+ default PA8X00
=20
config PA7000
bool "PA7000/PA7100"
--=20
1.7.7.6
--
To unsubscribe from this list: send the line "unsubscribe linux-parisc"=
in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html

Chen Gang

author

2013-07-24 08:27 UTC #1 lore raw

[Suggestion] parisc: kernel: about section mismatch warning.

Hello Maintainers:

When building parisc with allmodconfig by 'hppa64-linux-gnu-', I find section mismatch warnings.

I am not quite sure whether they will cause real issue or not, please help check, thanks.

LD arch/parisc/kernel/built-in.o
WARNING: arch/parisc/kernel/built-in.o(.data+0x118): Section mismatch in reference from the variable .L24 to the function .init.text:do_device_inventory() The variable .L24 references
the function __init do_device_inventory()
If the reference is valid then annotate the
variable with __init* or __refdata (see linux/init.h) or name the variable:
*_template, *_timer, *_sht, *_ops, *_probe, *_probe_one, *_console

WARNING: arch/parisc/kernel/built-in.o(.data+0x120): Section mismatch in reference from the variable .L26 to the function .init.text:parisc_pdc_chassis_init() The variable .L26 references
the function __init parisc_pdc_chassis_init()
If the reference is valid then annotate the
variable with __init* or __refdata (see linux/init.h) or name the variable:
*_template, *_timer, *_sht, *_ops, *_probe, *_probe_one, *_console

At least, I am sure it is not the source code issue, is it the cross- compiler's issue (need change suitable compiler), or just skip them ?

Welcome any suggestions or completions.

Thanks.
--
Chen Gang

James Bottomley

maintainer

2013-07-24 14:11 UTC #2 lore raw

Re: [Suggestion] parisc: kernel: about section mismatch warning.

Quoted 6 lines · Chen Gang

Hello Maintainers:
When building parisc with allmodconfig by 'hppa64-linux-gnu-', I find section mismatch warnings.
I am not quite sure whether they will cause real issue or not, please help check, thanks.

I think you need to try a new compiler before we start looking at issues that don't show up in our build. However, since it doesn't show up in the parisc build, I don't actually think it's real, since it's a temporary label in core code.

James

Chen Gang F T

2013-07-24 23:58 UTC #3 lore raw

Re: [Suggestion] parisc: kernel: about section mismatch warning.

Quoted 5 lines · James Bottomley

Quoted 4 lines · Chen Gang
Hello Maintainers:
When building parisc with allmodconfig by 'hppa64-linux-gnu-', I find section mismatch warnings.

Quoted 8 lines

Quoted 2 lines
I am not quite sure whether they will cause real issue or not, please help check, thanks.
I think you need to try a new compiler before we start looking at issues that don't show up in our build. However, since it doesn't show up in the parisc build, I don't actually think it's real, since it's a temporary label in core code.

OK, thanks, I should use a new compiler for it, I will continue.

And welcome any additional suggestions or completions (especially the information about parisc compiler).

Thanks.

Signature · 1 line

Chen Gang

Chen Gang

author

2013-07-29 08:49 UTC #4 lore raw

Re: [Suggestion] parisc: kernel: about section mismatch warning.

After use own built cross compiler (gcc-4.9.0, binutils-2.23.2 with 'hppa64-gchen-linux'), no the related warnings any more.

The original compiler which I used ('hppa64-linux-gnu') is incorrect.

:-)

Thanks.

Quoted 23 lines · Chen Gang F T

Quoted 5 lines · James Bottomley
Quoted 4 lines · Chen Gang
Hello Maintainers:
When building parisc with allmodconfig by 'hppa64-linux-gnu-', I find section mismatch warnings.
Quoted 8 lines
Quoted 2 lines
I am not quite sure whether they will cause real issue or not, please help check, thanks.
I think you need to try a new compiler before we start looking at issues that don't show up in our build. However, since it doesn't show up in the parisc build, I don't actually think it's real, since it's a temporary label in core code.
OK, thanks, I should use a new compiler for it, I will continue.
And welcome any additional suggestions or completions (especially the information about parisc compiler).
Thanks.

Signature · 1 line

Chen Gang

John David Anglin

2013-07-29 13:47 UTC #5 lore raw

Re: [Suggestion] parisc: kernel: about section mismatch warning.

Quoted 4 lines · Chen Gang

After use own built cross compiler (gcc-4.9.0, binutils-2.23.2 with 'hppa64-gchen-linux'), no the related warnings any more.
The original compiler which I used ('hppa64-linux-gnu') is incorrect.

I haven't seen the warning with any recent compiler and possibly your compiler selection versus CONFIG_64BIT was wrong. What does 'hppa64-linux-gnu -v' show?

gcc-4.9.0 is not released and any particular snapshot may be buggy. Suggest using 4.8 branch.

Dave
--
John David Anglin [email protected]

Helge Deller

maintainer

2013-07-29 18:23 UTC #6 lore raw

Re: [Suggestion] parisc: kernel: about section mismatch warning.

Quoted 5 lines · John David Anglin

Quoted 3 lines · Chen Gang
After use own built cross compiler (gcc-4.9.0, binutils-2.23.2 with 'hppa64-gchen-linux'), no the related warnings any more.

Quoted 8 lines

Quoted 1 line
The original compiler which I used ('hppa64-linux-gnu') is incorrect.
I haven't seen the warning with any recent compiler and possibly your compiler selection versus CONFIG_64BIT was wrong. What does 'hppa64-linux-gnu -v' show?
gcc-4.9.0 is not released and any particular snapshot may be buggy. Suggest using 4.8 branch.

Hi Chen,

I'm using the prebuilt cross-gcc package from Fedora (since my x86_64 machines run Fedora):
https://koji.fedoraproject.org/koji/packageinfo?packageID=13624 (cross-gcc)
https://koji.fedoraproject.org/koji/packageinfo?packageID=13623 (cross-binutils)

If you use debian/ubuntu you could use "alien" to convert it to a debian/ubuntu package.

Helge

Chen Gang

author

2013-07-30 00:48 UTC #7 lore raw

Re: [Suggestion] parisc: kernel: about section mismatch warning.

In reply to John David Anglin

Quoted 5 lines · John David Anglin

Quoted 3 lines · Chen Gang
After use own built cross compiler (gcc-4.9.0, binutils-2.23.2 with 'hppa64-gchen-linux'), no the related warnings any more.

Quoted 7 lines

Quoted 1 line
The original compiler which I used ('hppa64-linux-gnu') is incorrect.
I haven't seen the warning with any recent compiler and possibly your compiler
selection versus CONFIG_64BIT was wrong. What does 'hppa64-linux-gnu -v' show?

The incorrect compiler's information.

[root@dhcp122 linux-next]# rpm -qf /usr/bin/hppa64-linux-gnu-gcc
gcc-hppa64-linux-gnu-4.7.1-0.1.20120606.fc17.x86_64
[root@dhcp122 linux-next]# hppa64-linux-gnu-gcc -v
Using built-in specs.
COLLECT_GCC=hppa64-linux-gnu-gcc
COLLECT_LTO_WRAPPER=/usr/libexec/gcc/hppa64-linux-gnu/4.7.1/lto-wrapper
Target: hppa64-linux-gnu
Configured with: ../gcc-4.7.1-RC-20120606/configure --disable-dependency-tracking --disable-silent-rules --prefix=/usr --exec-prefix=/usr --bindir=/usr/bin --sbindir=/usr/sbin --sysconfdir=/etc --datadir=/usr/share --includedir=/usr/include --libexecdir=/usr/libexec --localstatedir=/var --sharedstatedir=/var/lib --mandir=/usr/share/man --infodir=/usr/share/info --build=x86_64-redhat-linux-gnu --host=x86_64-redhat-linux-gnu --target=hppa64-linux-gnu --enable-targets=all --program-prefix=hppa64-linux-gnu- --enable-languages=c --without-headers --enable-sjlj-exceptions --with-system-libunwind --disable-nls --disable-threads --disable-shared --disable-libmudflap --disable-libssp --disable-libgomp --disable-libquadmath --disable-gold --disable-decimal-float --enable-checking= --enable-gnu-uniqu
e-object --enable-linker-build-id --disable-plugin --enable-nls --with-system-zlib --with-bugurl=http://bugzilla.redhat.com/bugzilla/ --enable-obsolete
Thread model: single
gcc version 4.7.1 20120606 (Red Hat 4.7.1-0.1.20120606) (GCC)

Quoted 4 lines

gcc-4.9.0 is not released and any particular snapshot may be buggy. Suggest using
4.8 branch.

gcc-4.9.0 with binutil-2.23.2 for 'hppa64-linux' is correct for parisc with 'CONFIG_64BIT' enabled.

I intend to use gcc-4.9.0, (I want to find more issues not only for kernel, but also for gcc, so I can have more chances to provide my contributions for both of them)

;-)

Quoted 8 lines

Dave
Signature · 1 line
John David Anglin    [email protected]

Thanks.

Signature · 1 line

Chen Gang

James Bottomley

maintainer

2013-07-24 14:00 UTC #8 lore raw

In reply to Chen Gang

Quoted 1 line · Chen Gang

For server, 64-bit kernel is widely used and '64BIT' have been alread=

Quoted 4 lines

as the default option of a server.
=20
So better to use 64-bit kernel as default choise instead of 32-bit kernel.

I think this is irrelevant since we have defconfig for this. You apparent request doesn't match the code below.

Quoted 1 line

Or when use cross-compiler 'hppa64-linux-gnu-gcc' with allmodconfig, =

Quoted 4 lines

will report BUILD_BUG_ON:
=20
arch/parisc/mm/init.c: In function =E2=80=98mem_init=E2=80=99:
arch/parisc/mm/init.c:581:2: error: call to =E2=80=98__compiletime_=

assert_581=E2=80=99 declared with attribute error: BUILD_BUG_ON failed:=
PTE_ENTRY_SIZE !=3D sizeof(pte_t)

This shows you're using a buggy compiler. PTE_OFFSET_SIZE is generated as part of the build process, so you need a correct compiler.

Quoted 12 lines

Signed-off-by Chen Gang <[email protected]>
---
 arch/parisc/Kconfig |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)
=20
arch/parisc/Kconfig +0 -0
index aa399a5..37bdecf 100644
@@ -111,7 +111,7 @@ menu "Processor type and features"
=20
choice

arch/parisc/Kconfig

Quoted 3 lines

arch/parisc/Kconfig +1 -1

 	prompt "Processor type"
-	default PA7000
+	default PA8X00

This doesn't require 64 bit: PA8xxx processors can operate happily in 3= 2
bit mode it does make the question appear, since PA7xxx are 32 bit only= =2E

James

--
To unsubscribe from this list: send the line "unsubscribe linux-parisc"=
in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html

Chen Gang F T

2013-07-25 00:37 UTC #9 lore raw

Quoted 3 lines · James Bottomley

=20
Quoted 1 line · Chen Gang
For server, 64-bit kernel is widely used and '64BIT' have been alrea=

Quoted 8 lines

Quoted 4 lines
as the default option of a server.
So better to use 64-bit kernel as default choise instead of 32-bit kernel.
=20
I think this is irrelevant since we have defconfig for this. You apparent request doesn't match the code below.
=20

Hmm... but I still suggest when use 'allmodconfig' let 64-bit as the default choice (normally 64-bit is the default choice for servers).

Quoted 1 line

Quoted 1 line
Or when use cross-compiler 'hppa64-linux-gnu-gcc' with allmodconfig,=

Quoted 4 lines

Quoted 4 lines
will report BUILD_BUG_ON:
arch/parisc/mm/init.c: In function =E2=80=98mem_init=E2=80=99:
arch/parisc/mm/init.c:581:2: error: call to =E2=80=98__compiletime=

_assert_581=E2=80=99 declared with attribute error: BUILD_BUG_ON failed= : PTE_ENTRY_SIZE !=3D sizeof(pte_t)

Quoted 2 lines

=20
This shows you're using a buggy compiler. PTE_OFFSET_SIZE is generat=

Quoted 2 lines

as part of the build process, so you need a correct compiler. =20

Hmm... It means the compiler assumes to build 64-bit code (hppa64), but our configuration is for 32-bit, they are mismatch.

Maybe we can say hppa64-linux-gnu-gcc can not build the 32-bit parisc code (although it is not precise), but at least, it is not a real bug.

This contents wants to say: when use 'allmodconfig' for a server, we do not build a 64-bit server.

Quoted 5 lines

Quoted 5 lines
Signed-off-by Chen Gang <[email protected]>
---
 arch/parisc/Kconfig |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)

Quoted 12 lines

arch/parisc/Kconfig
Quoted 10 lines
arch/parisc/Kconfig +0 -0
index aa399a5..37bdecf 100644
@@ -111,7 +111,7 @@ menu "Processor type and features"
=20
choice
arch/parisc/Kconfig +1 -1
 	prompt "Processor type"
-	default PA7000
+	default PA8X00
=20
This doesn't require 64 bit: PA8xxx processors can operate happily in=

Quoted 1 line

bit mode it does make the question appear, since PA7xxx are 32 bit on=

ly.

Quoted 1 line

=20

Yeah, 'PA8X00' can compitable with 32-bit, but it likes 64-bit, the following config files are for 'PA8X00':

a500_defconfig: for 64-bit
c3000_defconfig: for 32-bit
c8000_defconfig: for 64-bit
generic-64bit_defconfig: for 64-bit

At least, we can say PA8xxx is a 64-bit processor for parisc, is it correct ?

And for 'allmodconfig', if let 'PA8X00' as default choice, it will buil= d
64-bit kernel.

Thanks.
--=20
Chen Gang

--=20
Chen Gang
--
To unsubscribe from this list: send the line "unsubscribe linux-parisc"=
in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html

Helge Deller

maintainer

2013-07-26 20:08 UTC #10 lore raw

Hi Chen,

Quoted 4 lines · Chen Gang F T

Quoted 3 lines · James Bottomley
Quoted 1 line · Chen Gang
For server, 64-bit kernel is widely used and '64BIT' have been alre=

ady

Quoted 6 lines

Quoted 6 lines
Quoted 4 lines
as the default option of a server.
So better to use 64-bit kernel as default choise instead of 32-bit kernel.
I think this is irrelevant since we have defconfig for this.

I do have the same opinion.
It's not necessary.

=46urthermore, for a real 64 bit kernel you need to enable CONFIG_64BIT not CONFIG_PA8X00.

Quoted 2 lines

Hmm... but I still suggest when use 'allmodconfig' let 64-bit as the default choice (normally 64-bit is the default choice for servers).

Yeah, but we do support workstations as well.

Quoted 1 line

Quoted 1 line
Quoted 1 line
Or when use cross-compiler 'hppa64-linux-gnu-gcc' with allmodconfig=

, it

Quoted 4 lines

Quoted 4 lines
Quoted 4 lines
will report BUILD_BUG_ON:
arch/parisc/mm/init.c: In function =E2=80=98mem_init=E2=80=99:
arch/parisc/mm/init.c:581:2: error: call to =E2=80=98__compiletim=

e_assert_581=E2=80=99 declared with attribute error: BUILD_BUG_ON faile=
d: PTE_ENTRY_SIZE !=3D sizeof(pte_t)

Quoted 2 lines

Quoted 2 lines
This shows you're using a buggy compiler. PTE_OFFSET_SIZE is genera=

ted

Quoted 4 lines

Quoted 2 lines
as part of the build process, so you need a correct compiler.
=20
Hmm... It means the compiler assumes to build 64-bit code (hppa64), b=

Quoted 4 lines

our configuration is for 32-bit, they are mismatch.
=20
Maybe we can say hppa64-linux-gnu-gcc can not build the 32-bit parisc code (although it is not precise), but at least, it is not a real bug=

=2E

It's a fact:
hppa64-linux-gnu-gcc can *not* build the 32-bit parisc. Only hppa-linux-gnu-gcc can build 32bit code.=20

Quoted 1 line

This contents wants to say: when use 'allmodconfig' for a server, we =

Quoted 4 lines

not build a 64-bit server.
=20
=20
Quoted 1 line
Quoted 1 line
Signed-off-by Chen Gang <[email protected]>

Thanks for your patch, but:
NAK.

Helge

Quoted 4 lines

---
 arch/parisc/Kconfig |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)

Quoted 12 lines

Quoted 4 lines
Quoted 4 lines
arch/parisc/Kconfig +0 -0
index aa399a5..37bdecf 100644
Quoted 8 lines
arch/parisc/Kconfig
Quoted 6 lines
arch/parisc/Kconfig +0 -0
@@ -111,7 +111,7 @@ menu "Processor type and features"
=20
choice
arch/parisc/Kconfig +1 -1
 	prompt "Processor type"
-	default PA7000
+	default PA8X00
This doesn't require 64 bit: PA8xxx processors can operate happily i=

n 32

Quoted 1 line

Quoted 1 line
bit mode it does make the question appear, since PA7xxx are 32 bit o=

nly.

Quoted 14 lines

Quoted 1 line
=20
Yeah, 'PA8X00' can compitable with 32-bit, but it likes 64-bit, the following config files are for 'PA8X00':
=20
a500_defconfig: for 64-bit
c3000_defconfig: for 32-bit
c8000_defconfig: for 64-bit
generic-64bit_defconfig: for 64-bit
=20
At least, we can say PA8xxx is a 64-bit processor for parisc, is it correct ?
=20
And for 'allmodconfig', if let 'PA8X00' as default choice, it will bu=

ild

Quoted 5 lines

64-bit kernel.
=20
=20
Thanks.
=20

--
To unsubscribe from this list: send the line "unsubscribe linux-parisc"=
in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html

Chen Gang

author

2013-07-29 01:11 UTC #11 lore raw

Quoted 7 lines · Helge Deller

Hi Chen,
=20
Quoted 4 lines · Chen Gang F T
Quoted 3 lines · James Bottomley
Quoted 1 line · Chen Gang
For server, 64-bit kernel is widely used and '64BIT' have been alr=

eady

Quoted 5 lines

Quoted 5 lines
Quoted 5 lines
Quoted 4 lines
as the default option of a server.
So better to use 64-bit kernel as default choise instead of 32-bit kernel.

Quoted 8 lines

Quoted 1 line
Quoted 1 line
I think this is irrelevant since we have defconfig for this.
=20
I do have the same opinion.
It's not necessary.
=20
Furthermore, for a real 64 bit kernel you need to enable CONFIG_64BIT not CONFIG_PA8X00.
=20

But for "allmodconfig", it can not enable 'CONFIG_64BIT' automatically.

Quoted 5 lines

Quoted 2 lines
Hmm... but I still suggest when use 'allmodconfig' let 64-bit as the default choice (normally 64-bit is the default choice for servers).
=20
Yeah, but we do support workstations as well.
=20

OH, thanks, I really don't know about it (today I know :-) ), in my original memory, parisc is mainly for server and well known by many mem= bers.

As far as I know, we often set mainly used item as default choice, if have several mainly used item, need set general or compatible item as default choice.

If 'PA8X00' is our mainly used item (only 'PA8X00' support 64-bit), I still suggest to set it as default choice. Or when 'allmodconfig' works for a server, finds 'CONFIG_64BIT' unset, it really wonders "Why ?"

Quoted 1 line

Quoted 1 line
Quoted 1 line
Quoted 1 line
Or when use cross-compiler 'hppa64-linux-gnu-gcc' with allmodconfi=

g, it

Quoted 4 lines

Quoted 4 lines
Quoted 4 lines
Quoted 4 lines
will report BUILD_BUG_ON:
arch/parisc/mm/init.c: In function =A1=AEmem_init=A1=AF:
arch/parisc/mm/init.c:581:2: error: call to =A1=AE__compiletime_=

assert_581=A1=AF declared with attribute error: BUILD_BUG_ON failed: PT= E_ENTRY_SIZE !=3D sizeof(pte_t)

Quoted 2 lines

Quoted 2 lines
Quoted 2 lines
This shows you're using a buggy compiler. PTE_OFFSET_SIZE is gener=

ated

Quoted 4 lines

Quoted 4 lines
Quoted 2 lines
as part of the build process, so you need a correct compiler.
Hmm... It means the compiler assumes to build 64-bit code (hppa64), =

but

Quoted 3 lines

Quoted 3 lines
our configuration is for 32-bit, they are mismatch.
Maybe we can say hppa64-linux-gnu-gcc can not build the 32-bit paris=

Quoted 1 line

Quoted 1 line
code (although it is not precise), but at least, it is not a real bu=

Quoted 6 lines

=20
It's a fact:
hppa64-linux-gnu-gcc can *not* build the 32-bit parisc. Only hppa-linux-gnu-gcc can build 32bit code.=20 =20
=20

Thank you for your confirmation.

I should build hppa-linux-gnu-gcc cross-compiler firstly.

Hmm... I try to finish it within this week (but not quite sure), but at least I should finish it within next month (2013-08-31).

Welcome any additional suggestions or completions (especially the related information for parisc cross-compiler).

Quoted 1 line

Quoted 1 line
This contents wants to say: when use 'allmodconfig' for a server, we=

Quoted 8 lines

Quoted 4 lines
not build a 64-bit server.
Quoted 1 line
Quoted 1 line
Signed-off-by Chen Gang <[email protected]>
=20
Thanks for your patch, but:
NAK.
=20

OK, I can understand.

Thank you too.

Quoted 18 lines

Helge
=20
Quoted 16 lines
Quoted 16 lines
Quoted 11 lines
---
 arch/parisc/Kconfig |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)
arch/parisc/Kconfig +0 -0
index aa399a5..37bdecf 100644
@@ -111,7 +111,7 @@ menu "Processor type and features"
=20
choice
arch/parisc/Kconfig
Quoted 3 lines
arch/parisc/Kconfig +1 -1
 	prompt "Processor type"
-	default PA7000
+	default PA8X00
This doesn't require 64 bit: PA8xxx processors can operate happily =

in 32

Quoted 1 line

Quoted 1 line
Quoted 1 line
bit mode it does make the question appear, since PA7xxx are 32 bit =

only.

Quoted 10 lines

Quoted 10 lines
Quoted 1 line
Yeah, 'PA8X00' can compitable with 32-bit, but it likes 64-bit, the following config files are for 'PA8X00':
a500_defconfig: for 64-bit
c3000_defconfig: for 32-bit
c8000_defconfig: for 64-bit
generic-64bit_defconfig: for 64-bit

Quoted 4 lines

Quoted 4 lines
At least, we can say PA8xxx is a 64-bit processor for parisc, is it correct ?
And for 'allmodconfig', if let 'PA8X00' as default choice, it will b=

uild

Quoted 6 lines

Quoted 5 lines
64-bit kernel.
Thanks.
=20

--=20
Chen Gang

Chen Gang

author

2013-07-29 08:39 UTC #12 lore raw

[Suggestion] parisc: about the warnings "unsigned expression < 0 is always false"

Hello Maintainers:

Are the warnings real issue (I guess so, but don't know how to fix) ?

Please help check, thanks.

The cross compiler is built from (gcc-4.9.0 and binutils-2.23.2 with 'hppa-gchen-linux'), the related warnings (for 'allmodconfig'):

In file included from arch/parisc/math-emu/fmpyfadd.c:50:0:
arch/parisc/math-emu/fmpyfadd.c: In function 'dbl_fmpyfadd':
arch/parisc/math-emu/dbl_float.h:755:30: warning: comparison of unsigned expression < 0 is always false [-Wtype-limits]

  if ((unsigned int)(src1dstD += (src2D)) < (unsigned int)(src2D)) { \
                              ^

arch/parisc/math-emu/fmpyfadd.c:394:4: note: in expansion of macro 'Fourword_add'
Fourword_add(tmpresp1, tmpresp2, tmpresp3, tmpresp4,
^
arch/parisc/math-emu/dbl_float.h:765:33: warning: comparison of unsigned expression < 0 is always false [-Wtype-limits]

     if ((unsigned int)(src1dstC += (src2C)) <   \
   
                              ^

:-)

Thanks.
--
Chen Gang