The following reply was made to PR c/10735; it has been noted by GNATS.

From: "Alexander V. Inyukhin" <shurick@pisem.net>
To: Dara Hazeghi <dhazeghi@yahoo.com>
Cc: gcc-gnats@gcc.gnu.org
Subject: Re: c/10735: Crash on incorrect type conversion
Date: Sun, 11 May 2003 03:34:10 +0400

 On Sat, May 10, 2003 at 04:24:20PM -0700, Dara Hazeghi wrote:
 > http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit- 
 > trail&database=gcc&pr=10735
 > 
 > Hello,
 > 
 > you don't mention a platform in your bug report, nor do you give the  
 > exact error message. Both are essential to tracking down your bug.  
 > Could you please add them (just replying to this message will do so).  
 > Also, if possible, can you try your testcase on gcc 3.2.3? Thanks,
 
 Sorry, I forget to add this.
 
 Reading specs from /opt/gcc-3.2.3/lib/gcc-lib/i686-pc-linux-gnu/3.2.3/specs
 Configured with: ./configure --prefix=/opt/gcc-3.2.3 --enable-__cxa_atexit --enable-threads=posix --enable-shared
 Thread model: posix
 gcc version 3.2.3
 
 $ /opt/gcc-3.2.3/bin/gcc 1.c -mmmx
 1.c: In function `test':
 1.c:7: internal error: Segmentation fault
 Please submit a full bug report,
 with preprocessed source if appropriate.
 See <URL:http://gcc.gnu.org/bugs.html> for instructions.
 
 
 
 
 åxample below handled correctly by gcc:
 
 typedef int __v4hi __attribute__ ((__mode__ (__V4HI__)));
 
 __v4hi test3;
 
 void test()
 {
 	long long test4;
 	test4 = test3;  // <== incompatible types in assignment
 	if (test4 != 0)
 	return;
 }