[Bug c++/16981] New: Different output between g++3.5 on Mac and g++3.3.3 on Suses

[Bug c++/16981] New: Different output between g++3.5 on Mac and g++3.3.3 on Suses

[yanliu at ca dot ibm dot com]

Using g++3.5 on powerpc Apple MacOS system, I am getting different execution
result than using g++3.3.
With g++3.5, the execution result is:
The size of c0=8 and of c1=12 and c1::c0=8
Byte 0 has value 0
Byte 1 has value 0
Byte 2 has value 0
Byte 3 has value 0
Byte 4 has value 0
Byte 5 has value 0
Byte 6 has value 0
Byte 7 has value 0
Byte 8 has value 63
Byte 9 has value -128
Byte 10 has value 0
Byte 11 has value 0

With g++3.3(gcc version 3.3.3 on SuSE Linux), the execution result is:
The size of c0=8 and of c1=12 and c1::c0=8
Byte 0 has value 0
Byte 1 has value 0
Byte 2 has value 0
Byte 3 has value 0
Byte 4 has value 0
Byte 5 has value 0
Byte 6 has value 0
Byte 7 has value 0
Byte 8 has value 63
Byte 9 has value 128
Byte 10 has value 0
Byte 11 has value 0

Byte 9 has different values for the two compilers. I am not sure the comparison
between different gcc versions on different platforms are valid or not. But
running g++3.3 on MacOS, gives the same result as g++3.5 on MacOS. Could you
please verify if this is compiler regression? Thanks.

-- 
           Summary: Different output between g++3.5 on Mac and g++3.3.3 on
                    Suses
           Product: gcc
           Version: 3.5.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: c++
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: yanliu at ca dot ibm dot com
                CC: gcc-bugs at gcc dot gnu dot org
  GCC host triplet: gcc version 3.5.0-tree-ssa 20040321 (merged 20040529)
                    (Apple Com


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=16981

[Bug c++/16981] Different output between g++3.5 on Mac and g++3.3.3 on Suses

[yanliu at ca dot ibm dot com]

------- Additional Comments From yanliu at ca dot ibm dot com  2004-08-11 15:38 -------
Created an attachment (id=6915)
 --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=6915&action=view)
testcase

Steps to reproduce the problem:
g++ t.C
a.out

-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=16981

[Bug c++/16981] Different output between g++3.5 on Mac and g++3.3.3 on Suses

[pinskia at gcc dot gnu dot org]

------- Additional Comments From pinskia at gcc dot gnu dot org  2004-08-11 16:02 -------
Not a bug, char on Darwin is signed by default but char on PPC Linux is unsigned by default.

-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |RESOLVED
         Resolution|                            |INVALID


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=16981

[Bug c++/16981] Different output between g++3.5 on Mac and g++3.3.3 on Suses

[bangerth at dealii dot org]

------- Additional Comments From bangerth at dealii dot org  2004-08-11 17:43 -------
I get the exact same output for 3.3.4, 3.4.1 and mainline on my x86 
linux box. 
 
W. 

-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=16981