[Bug c/10735] ICE on incorrect type conversion with vector
shurick@pisem.net
gcc-bugzilla@gcc.gnu.org
Mon Jun 2 14:30:00 GMT 2003
PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=10735
------- Additional Comments From shurick@pisem.net 2003-06-02 14:30 -------
Subject: Re: ICE on incorrect type conversion with vector
pinskia@physics.uc.edu wrote:
>PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org.
>
>http://gcc.gnu.org/bugzilla/show_bug.cgi?id=10735
>
>
>pinskia@physics.uc.edu changed:
>
> What |Removed |Added
>----------------------------------------------------------------------------
> Summary|Crash on incorrect type |ICE on incorrect type
> |conversion |conversion with vector
>
>
>
Really this type conversion is right. The second example (with warning
instead of ICE) does not contain conversion by a mistake (my fault).
Correct example is:
typedef int __v4hi __attribute__ ((__mode__ (__V4HI__)));
__v4hi test3;
void test()
{
long long test4;
test4 = (long long)test3; // <== "(long long)" was skipped
if (test4 != 0)
return;
}
So, it should be called like "ICE on correct type conversion with vector".
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
More information about the Gcc-bugs
mailing list