Bug#443576: Strict aliasing problem
"Phil Endecott" <[EMAIL PROTECTED]> writes:
>> I think I found a bug in gcc-4.2
>
>> int i, j;
>> printf("%d %d\n", j, (void *)(j));
>
> This looks like a strict-aliasing issue to me; you're casting from an
> int to a void*, which is undefined.
Casting from int to void* is not undefined, but implementation
defined. Also, this clearly has nothing to do with aliasing, since
aliasing is about accessing objects using an lvalue of a bad type, and
not about casting.
I would rather guess this is the same problem as #440545 (caused by a
bug in SCEV).
--
Falk
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#443576: Strict aliasing problem
Le 23.09.2007, à 10:22:15, Falk Hueffner a écrit:
> "Phil Endecott" <[EMAIL PROTECTED]> writes:
>
> >> I think I found a bug in gcc-4.2
> >
> >> int i, j;
> >> printf("%d %d\n", j, (void *)(j));
> >
> > This looks like a strict-aliasing issue to me; you're casting from an
> > int to a void*, which is undefined.
>
> Casting from int to void* is not undefined, but implementation
> defined. Also, this clearly has nothing to do with aliasing, since
> aliasing is about accessing objects using an lvalue of a bad type, and
> not about casting.
>
> I would rather guess this is the same problem as #440545 (caused by a
> bug in SCEV).
It looks like the same bug. The bug was discovered when using the glib
GINT_TO_POINTER() macro. Exactly as in #440545.
The sample code provided in #440545 is also very similar to mine.
The upstream bug report (http://gcc.gnu.org/PR33381) has a patch
included. So I hope the bug will not stay opened too long.
Maybe Debian will have to auto-rebuild the complete archive after the
bug is solved to remove any miss-compiled code.
Thanks
--
Dr. Ludovic Rousseau[EMAIL PROTECTED]
-- Normaliser Unix c'est comme pasteuriser le camembert, L.R. --
Bug#443744: gdc-4.1: undefined reference to `_D3std1c5stdio6_iobuf6__initZ'
Package: gdc-4.1
Version: 0.24-4.1.2-16
Severity: grave
Justification: renders package unusable
$ cat test.d
import std.c.stdio;
int main()
{
FILE *files[1] = [stdin];
return 0;
}
$ gdc -o /dev/null test.d
/tmp/cc2CdHzH.o:(.data._D29TypeInfo_S3std1c5stdio6_iobuf6__initZ[_D29TypeInfo_S3std1c5stdio6_iobuf6__initZ]+0x28):
undefined reference to `_D3std1c5stdio6_iobuf6__initZ'
collect2: ld returned 1 exit status
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Processed: found 442036 in 4.2.1-5, notfound 442036 in 4:4.2.1-6
Processing commands for [EMAIL PROTECTED]: > # Automatically generated email from bts, devscripts version 2.10.8 > found 442036 4.2.1-5 Bug#442036: gcc-4.2: ICE on Alpha with new GSL sources Bug marked as found in version 4.2.1-5. > notfound 442036 4:4.2.1-6 Bug#442036: gcc-4.2: ICE on Alpha with new GSL sources Bug no longer marked as found in version 4:4.2.1-6. > End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Processed: found 443576 in 4.2.1-4
Processing commands for [EMAIL PROTECTED]: > # Automatically generated email from bts, devscripts version 2.10.8 > found 443576 4.2.1-4 Bug#443576: gcc-4.2: -O2 generates wrong code Bug marked as found in version 4.2.1-4. > End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Processed: severity of 440545 is critical
Processing commands for [EMAIL PROTECTED]: > # Automatically generated email from bts, devscripts version 2.10.8 > severity 440545 critical Bug#440545: [PR33381] [amd64] miscompilation casting signed long to void* Severity set to `critical' from `normal' > End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#443767: libstdc++6-4.1-dev: libstdc++-dev doesn't need to depend on g++; recommend or suggest is sufficient
Package: libstdc++6-4.1-dev Version: 4.1.1-14 Severity: normal Hi, Currently libstdc++6-4.1-dev depends on g++-4.1, and vice-versa. While I think it's reasonable for g++ to depend on libstdc++-dev, I don't see a good reason why libstdc++-dev must depend on g++, and I suggest that this is reduced to a Recommends: or Suggests:. In my case I wanted to install libstdc++-dev to use with a cross-compiler on another machine, with the libstdc++ include files visible via an NFS mount. See this thread for the details: http://thread.gmane.org/gmane.linux.debian.devel.gcc/25092 Thanks, Phil. -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.19 Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Versions of packages libstdc++6-4.1-dev depends on: ii g++-4.1 4.1.1-14The GNU C++ compiler ii gcc-4.1-base 4.1.1-14The GNU Compiler Collection (base ii libc6-dev2.3.6.ds1-4 GNU C Library: Development Librari ii libstdc++6 4.1.1-14The GNU Standard C++ Library v3 libstdc++6-4.1-dev recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
gcj-4.1 4.1.2-16 MIGRATED to testing
FYI: The status of the gcj-4.1 source package in Debian's testing distribution has changed. Previous version: 4.1.2-14 Current version: 4.1.2-16 -- This email is automatically generated; [EMAIL PROTECTED] is responsible. See http://people.debian.org/~henning/trille/ for more information. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
