Compiler errors.

Compiler errors.

[Marko Saukko]

[-- Attachment #1: Type: text/plain, Size: 1800 bytes --]

Hi,

with the latest oFono git version I'm getting the following compiler
errors when using gcc (Ubuntu 4.3.3-5ubuntu4) 4.3.3.

----

gcc -DHAVE_CONFIG_H -I. -I.. -I../include -I../src
-I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include   -g -O2 -Werror
-Wextra -Wno-unused-parameter -Wno-missing-field-initializers
-Wdeclaration-after-statement -Wmissing-declarations -Wredundant-decls
-Wcast-align -MT smsutil.o -MD -MP -MF .deps/smsutil.Tpo -c -o smsutil.o
`test -f '../src/smsutil.c' || echo './'`../src/smsutil.c
cc1: warnings being treated as errors
../src/smsutil.c: In function ‘sms_extract_common’:
../src/smsutil.c:1442: error: ‘dcs’ may be used uninitialized in this
function
../src/smsutil.c:1441: error: ‘udhi’ may be used uninitialized in this
function
../src/smsutil.c:1440: error: ‘max’ may be used uninitialized in this
function
../src/smsutil.c:1439: error: ‘udl’ may be used uninitialized in this
function
../src/smsutil.c: In function ‘extract_app_port_common’:
../src/smsutil.c:1756: error: ‘is_addr_8bit’ may be used uninitialized
in this function
../src/smsutil.c: In function ‘sms_extract_concatenation’:
../src/smsutil.c:1843: error: ‘seq’ may be used uninitialized in this
function
../src/smsutil.c:1843: error: ‘max’ may be used uninitialized in this
function
../src/smsutil.c:1842: error: ‘rn’ may be used uninitialized in this
function
../src/smsutil.c: In function ‘cbs_decode_text’:
../src/smsutil.c:2706: error: ‘iso639’ may be used uninitialized in this
function
../src/smsutil.c:2704: error: ‘charset’ may be used uninitialized in
this function
make[2]: *** [smsutil.o] Error 1
make[2]: Leaving directory `/home/muk/software/ofono/ofono/unit'

----

Regards,
Marko

Re: Compiler errors.

[Marcel Holtmann]

[-- Attachment #1: Type: text/plain, Size: 991 bytes --]

Hi Marko,

> with the latest oFono git version I'm getting the following compiler
> errors when using gcc (Ubuntu 4.3.3-5ubuntu4) 4.3.3.
> 
> ----
> 
> gcc -DHAVE_CONFIG_H -I. -I.. -I../include -I../src
> -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include   -g -O2 -Werror
> -Wextra -Wno-unused-parameter -Wno-missing-field-initializers
> -Wdeclaration-after-statement -Wmissing-declarations -Wredundant-decls
> -Wcast-align -MT smsutil.o -MD -MP -MF .deps/smsutil.Tpo -c -o smsutil.o
> `test -f '../src/smsutil.c' || echo './'`../src/smsutil.c
> cc1: warnings being treated as errors
> ../src/smsutil.c: In function ‘sms_extract_common’:
> ../src/smsutil.c:1442: error: ‘dcs’ may be used uninitialized in this
> function
> ../src/smsutil.c:1441: error: ‘udhi’ may be used uninitialized in this
> function

I didn't see them when building the release, but some distro compilers
are a different.

Denis, care to fix these please.

Regards

Marcel

Re: Compiler errors.

[Marcel Holtmann]

[-- Attachment #1: Type: text/plain, Size: 208 bytes --]

Hi Marko,

> with the latest oFono git version I'm getting the following compiler
> errors when using gcc (Ubuntu 4.3.3-5ubuntu4) 4.3.3.

so Denis and I fixed all of these now.

Regards

Marcel

compiler errors

[satadru pramanik]

I was compiling glib-1.1.2, and came up with an internal compiler error.
I have glibc .961212-1o

Should I complain, or move on to glibc2?
Errors:
testglib.c:966: internal error--unrecognizable insn:
(insn 9133 9130 9134 (set (mem:SI (plus:SI (reg:SI 16 r16)
                (const_int 65536)))
        (reg:SI 17 r17)) -1 (insn_list 5710 (insn_list 9130 (insn_list:REG_DEP_OUTPUT 5741 (insn_list:REG_DEP_OUTPUT 5713 (insn_list:REG_DEP_OUTPUT 5729 (insn_list:REG_DEP_OUTPUT 5736 (insn_list:REG_DEP_OUTPUT 5752 (insn_list:REG_DEP_OUTPUT 5764 (insn_list:REG_DEP_OUTPUT 5759 (insn_list:REG_DEP_OUTPUT 5772 (insn_list:REG_DEP_OUTPUT 5784 (insn_list:REG_DEP_OUTPUT 5779 (insn_list:REG_DEP_OUTPUT 5799 (insn_list:REG_DEP_OUTPUT 9126 (insn_list:REG_DEP_OUTPUT 9129 (nil))))))))))))))))
    (nil))
toplev.c:1360: Internal compiler error in function fatal_insn
make: *** [testglib.o] Error 1
[user@real glib-1.1.12]# 


[[ This message was sent via the linuxppc-dev mailing list. Replies are ]]
[[ not forced back to the list, so be sure to  Cc linuxppc-dev  if your ]]
[[ reply is of general interest. To unsubscribe from linuxppc-dev, send ]]
[[ the message 'unsubscribe' to linuxppc-dev-request@lists.linuxppc.org ]]

Re: compiler errors

[David Edelsohn]

	You do not mention which release of EGCS you are using.  This may
have been fixed in egcs-1.1.1, but you need to use Gary Thomas's special
build of egcs-1.1.1 unless your system is running glibc2.1.

David

[[ This message was sent via the linuxppc-dev mailing list. Replies are ]]
[[ not forced back to the list, so be sure to  Cc linuxppc-dev  if your ]]
[[ reply is of general interest. To unsubscribe from linuxppc-dev, send ]]
[[ the message 'unsubscribe' to linuxppc-dev-request@lists.linuxppc.org ]]

Re: compiler errors

[satadru pramanik]

egcs 1.1.1c
cheers,
sat.


On Wed, 13 Jan 1999, David Edelsohn wrote:

	You do not mention which release of EGCS you are using.  This may
have been fixed in egcs-1.1.1, but you need to use Gary Thomas's special
build of egcs-1.1.1 unless your system is running glibc2.1.

David



----
satadru pramanik `satadru@umich.edu'
"Put your hand on a hot stove for a minute, and it seems like an hour. Sit
with a pretty girl for an hour, and it seems like a minute. THAT'S
relativity." 
-Albert Einstein
---


[[ This message was sent via the linuxppc-dev mailing list. Replies are ]]
[[ not forced back to the list, so be sure to  Cc linuxppc-dev  if your ]]
[[ reply is of general interest. To unsubscribe from linuxppc-dev, send ]]
[[ the message 'unsubscribe' to linuxppc-dev-request@lists.linuxppc.org ]]

Re: compiler errors

[David Edelsohn]

>>>>> satadru pramanik writes:

satadru> egcs 1.1.1c

	Hmm, well I thought that problem had been addressed in egcs-1.1.1.
The problem is that GCC is generating a memory reference with a
displacement (65536) which is larger than 16 bits.  Someone needs to try
to track down why the PowerPC port thinks that is a valid address instead
of splitting it into an intermediate offset in a register.

	Either GCC is generating that offset itself and the normal tests
for valid types of addressing are failing.  Or, something in the PowerPC
port explicitly is generating a memory operation which bypasses the tests
and is not explicitly checking for exceeding this offset limit.

David

[[ This message was sent via the linuxppc-dev mailing list. Replies are ]]
[[ not forced back to the list, so be sure to  Cc linuxppc-dev  if your ]]
[[ reply is of general interest. To unsubscribe from linuxppc-dev, send ]]
[[ the message 'unsubscribe' to linuxppc-dev-request@lists.linuxppc.org ]]