<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 12pt;
font-family:Calibri
}
--></style></head>
<body class='hmmessage'><div dir='ltr'>You are right, it isn't new. But I think nothing in the system was using it until the 32bit wchar support came in.<div>I added test p257 that exercises it..so I can make sure m3cc/nt386 agree, and then update C backend to match.</div><div><br></div><div> - Jay<br><br><br><br><div>> Subject: Re: [M3devel] m3cg right shift signed?<br>> From: hosking@purdue.edu<br>> Date: Mon, 8 Jun 2015 22:00:22 -0400<br>> CC: m3devel@elegosoft.com<br>> To: jay.krell@cornell.edu<br>> <br>> I don’t think this is a new occurrence. Surely signed right shift makes sense to retain the sign bit?<br>> <br>> > On Jun 8, 2015, at 9:44 PM, Jay <jay.krell@cornell.edu> wrote:<br>> > <br>> > (Not at propercomputer but sending anyway.)<br>> > <br>> > Is right shift of a signed type meant to be supported and well defined in the IR? I thought not, and assert so in the C backend. But it occurs now, from m3front/cg/set_range or such. Maybe change that to not? Surely unsigned types are adequate here?<br>> > <br>> > - Jay<br>> <br></div></div> </div></body>
</html>