<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 10pt;
font-family:Tahoma
}
--></style>
</head>
<body class='hmmessage'>
Try building m3-sys/m3tests/p2/p240.<br>There is an error in the configure enable-checking about the types being mismatched.<br><br> - Jay<br><br><br>> From: hosking@cs.purdue.edu<br>> Date: Tue, 23 Nov 2010 09:48:19 -0500<br>> To: jkrell@elego.de<br>> CC: m3commit@elegosoft.com<br>> Subject: Re: [M3commit] CVS Update: cm3<br>> <br>> <br>> On Nov 23, 2010, at 10:49 AM, Jay Krell wrote:<br>> <br>> > CVSROOT: /usr/cvs<br>> > Changes by: jkrell@birch. 10/11/23 10:49:57<br>> > <br>> > Modified files:<br>> > cm3/m3-sys/m3cc/gcc/gcc/m3cg/: parse.c <br>> > <br>> > Log message:<br>> > Go with the obvious less heavy handed fix of only avoiding<br>> > fold for integer division.<br>> <br>> I don't understand what the issue is with folding on integer division. Please explain.<br>> <br>> > This is enough for test p240 and the unoptimized code is definitely better.<br>> > NOT fully tested, but really probably works.<br>> > It is probably worth digging into the frontend to see if there is a difference<br>> > in the types. It is probably also worth digging in the backend, like,<br>> > we do put in the casts consistently, why are they only not effective<br>> > for divide? I realize that a little bit of analysis goes a long way<br>> > on many divide cases: "divide tends to produce small results", sort of.<br>> > On the other hand, it isn't worth too much effort.<br>> > Divide is the slowest least used integer operation.<br>> <br> </body>
</html>