<html><head><base href="x-msg://498/"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">That should be handled by placing an appropriate cast in the gcc tree.<div>
<br><div><div>On Nov 23, 2010, at 1:45 PM, Jay K wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><span class="Apple-style-span" style="border-collapse: separate; font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-size: medium; "><div class="hmmessage" style="font-size: 10pt; font-family: Tahoma; ">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:<span class="Apple-converted-space"> </span><a href="mailto:hosking@cs.purdue.edu">hosking@cs.purdue.edu</a><br>> Date: Tue, 23 Nov 2010 09:48:19 -0500<br>> To:<span class="Apple-converted-space"> </span><a href="mailto:jkrell@elego.de">jkrell@elego.de</a><br>> CC:<span class="Apple-converted-space"> </span><a href="mailto:m3commit@elegosoft.com">m3commit@elegosoft.com</a><br>> Subject: Re: [M3commit] CVS Update: cm3<br>><span class="Apple-converted-space"> </span><br>><span class="Apple-converted-space"> </span><br>> On Nov 23, 2010, at 10:49 AM, Jay Krell wrote:<br>><span class="Apple-converted-space"> </span><br>> > CVSROOT: /usr/cvs<br>> > Changes by: jkrell@birch. 10/11/23 10:49:57<br>> ><span class="Apple-converted-space"> </span><br>> > Modified files:<br>> > cm3/m3-sys/m3cc/gcc/gcc/m3cg/: parse.c<span class="Apple-converted-space"> </span><br>> ><span class="Apple-converted-space"> </span><br>> > Log message:<br>> > Go with the obvious less heavy handed fix of only avoiding<br>> > fold for integer division.<br>><span class="Apple-converted-space"> </span><br>> I don't understand what the issue is with folding on integer division. Please explain.<br>><span class="Apple-converted-space"> </span><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>><span class="Apple-converted-space"> </span><br></div></span></blockquote></div><br></div></body></html>