<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<?xml-stylesheet href="http://www.blogger.com/styles/atom.css" type="text/css"?>
<feed xmlns="http://www.w3.org/2005/Atom">
  <id>http://groups.google.com/group/cxprop-users</id>
  <title type="text">cXprop users Google Group</title>
  <subtitle type="text">
  This is the users group for people using the cXprop tool.
  </subtitle>
  <link href="/group/cxprop-users/feed/atom_v1_0_topics.xml" rel="self" title="cXprop users feed"/>
  <updated>-0-0T::Z</updated>
  <generator uri="http://groups.google.com" version="1.99">Google Groups</generator>
  <entry>
  <author>
  <name>Nathan Cooprider</name>
  <email>ncoopri...@gmail.com</email>
  </author>
  <updated>2009-01-31T20:02:23Z</updated>
  <id>http://groups.google.com/group/cxprop-users/browse_frm/thread/8cdfd961d3036327</id>
  <link href="http://groups.google.com/group/cxprop-users/browse_frm/thread/8cdfd961d3036327" />
  <title type="html">Re: cXprop/CComp: reporting 2 bugs</title>
  <summary type="html" xml:space="preserve">
  Aurélien - &lt;br&gt; I looked into the two bugs you mentioned today. Unfortunately, the first &lt;br&gt; problem occurs inside CIL&#39;s parser and not in cXprop. The current &lt;br&gt; version of CIL still does not deal with labels for operands in inline &lt;br&gt; assembly, and adding that feature to their parser is beyond what I have &lt;br&gt; time to do. If you were to get it updated in CIL, I could then update
  </summary>
  </entry>
  <entry>
  <author>
  <name>Nathan Cooprider</name>
  <email>c...@cs.utah.edu</email>
  </author>
  <updated>2008-04-15T18:41:17Z</updated>
  <id>http://groups.google.com/group/cxprop-users/browse_frm/thread/e0f88a013a193764</id>
  <link href="http://groups.google.com/group/cxprop-users/browse_frm/thread/e0f88a013a193764" />
  <title type="html">Updated instructions for CComp</title>
  <summary type="html" xml:space="preserve">
  Thanks to a bug report from Fernando Magno Quintao Pereira at UCLA, I &lt;br&gt; found out the posted CComp distribution has a number of bugs. I updated &lt;br&gt; the distribution and the instructions. Sorry.
  </summary>
  </entry>
  <entry>
  <author>
  <name>Nathan Cooprider</name>
  <email>c...@cs.utah.edu</email>
  </author>
  <updated>2008-03-13T16:24:44Z</updated>
  <id>http://groups.google.com/group/cxprop-users/browse_frm/thread/3d5e286c63aac0df</id>
  <link href="http://groups.google.com/group/cxprop-users/browse_frm/thread/3d5e286c63aac0df" />
  <title type="html">New pdfs</title>
  <summary type="html" xml:space="preserve">
  I put up pdf versions of a number of the talks we have done about cXprop &lt;br&gt; and CComp. &lt;br&gt; &lt;a target=&quot;_blank&quot; rel=nofollow href=&quot;http://www.cs.utah.edu/~coop/research/cxprop&quot;&gt;[link]&lt;/a&gt; &lt;br&gt; &lt;a target=&quot;_blank&quot; rel=nofollow href=&quot;http://www.cs.utah.edu/~coop/research/ccomp&quot;&gt;[link]&lt;/a&gt;
  </summary>
  </entry>
  <entry>
  <author>
  <name>Nathan Cooprider</name>
  <email>c...@cs.utah.edu</email>
  </author>
  <updated>2008-01-21T17:24:29Z</updated>
  <id>http://groups.google.com/group/cxprop-users/browse_frm/thread/2ae62ffe8fe93823</id>
  <link href="http://groups.google.com/group/cxprop-users/browse_frm/thread/2ae62ffe8fe93823" />
  <title type="html">New slides!</title>
  <summary type="html" xml:space="preserve">
  John Regehr presented the research behind cXprop this past weekend at &lt;br&gt; the Washington University in St. Louis. You can find the slides here: &lt;br&gt; &lt;a target=&quot;_blank&quot; rel=nofollow href=&quot;http://www.cs.utah.edu/~coop/research/cxprop/washu08.ppt&quot;&gt;[link]&lt;/a&gt;
  </summary>
  </entry>
  <entry>
  <author>
  <name>Nathan Cooprider</name>
  <email>c...@cs.utah.edu</email>
  </author>
  <updated>2007-12-13T16:57:05Z</updated>
  <id>http://groups.google.com/group/cxprop-users/browse_frm/thread/5003538ffdbaa34b</id>
  <link href="http://groups.google.com/group/cxprop-users/browse_frm/thread/5003538ffdbaa34b" />
  <title type="html">Substantial update pending</title>
  <summary type="html" xml:space="preserve">
  John Regehr submitted a bug last night that led me to discover I had &lt;br&gt; accidentally written over the native machine dependency file. So anybody &lt;br&gt; running cXprop for normal desktop programs has probably been getting &lt;br&gt; incorrect answers. &lt;br&gt; This bug has been lurking since I added the 8051 machine dependency file
  </summary>
  </entry>
  <entry>
  <author>
  <name>Nathan Cooprider</name>
  <email>c...@cs.utah.edu</email>
  </author>
  <updated>2007-11-20T17:25:31Z</updated>
  <id>http://groups.google.com/group/cxprop-users/browse_frm/thread/c778909bd62709bc</id>
  <link href="http://groups.google.com/group/cxprop-users/browse_frm/thread/c778909bd62709bc" />
  <title type="html">Sydney talk</title>
  <summary type="html" xml:space="preserve">
  John Regehr presented our work for cXprop in Sydney Australia earlier &lt;br&gt; this month. The slides for that presentation can be found here: &lt;br&gt; &lt;a target=&quot;_blank&quot; rel=nofollow href=&quot;http://www.cs.utah.edu/~coop/research/cxprop/sydney07.ppt&quot;&gt;[link]&lt;/a&gt; &lt;br&gt; Most of this describes work we have already done, but the triggering and &lt;br&gt; sequencing ideas are future work.
  </summary>
  </entry>
  <entry>
  <author>
  <name>jonathan heusser</name>
  <email>jonathan.heus...@googlemail.com</email>
  </author>
  <updated>2007-11-16T11:55:02Z</updated>
  <id>http://groups.google.com/group/cxprop-users/browse_frm/thread/12008014cb24bde6</id>
  <link href="http://groups.google.com/group/cxprop-users/browse_frm/thread/12008014cb24bde6" />
  <title type="html">output of state</title>
  <summary type="html" xml:space="preserve">
  Hi Nathan, &lt;br&gt; &lt;p&gt;I&#39;m posting here in case other users have similar questions. &lt;br&gt; Is there a way to output the abstract variable state after the &lt;br&gt; analysis ? E.g. when using the interval domain it would output { l = &lt;br&gt; [0 20], h = [1 19], ... } or something. &lt;br&gt; &lt;p&gt;thanks &lt;br&gt; Jonathan
  </summary>
  </entry>
  <entry>
  <author>
  <name>Nathan Cooprider</name>
  <email>c...@cs.utah.edu</email>
  </author>
  <updated>2007-11-13T20:49:53Z</updated>
  <id>http://groups.google.com/group/cxprop-users/browse_frm/thread/95d1f2512c0ffb38</id>
  <link href="http://groups.google.com/group/cxprop-users/browse_frm/thread/95d1f2512c0ffb38" />
  <title type="html">Updated version</title>
  <summary type="html" xml:space="preserve">
  I updated the source download on the CComp website. So the current &lt;br&gt; version of cXprop/CComp can be found here: &lt;br&gt; &lt;a target=&quot;_blank&quot; rel=nofollow href=&quot;http://www.cs.utah.edu/~coop/research/ccomp/cil-cXprop.tgz&quot;&gt;[link]&lt;/a&gt;
  </summary>
  </entry>
  <entry>
  <author>
  <name>Nathan Cooprider</name>
  <email>c...@cs.utah.edu</email>
  </author>
  <updated>2007-11-01T20:33:35Z</updated>
  <id>http://groups.google.com/group/cxprop-users/browse_frm/thread/5ad413e66c66b3b0</id>
  <link href="http://groups.google.com/group/cxprop-users/browse_frm/thread/5ad413e66c66b3b0" />
  <title type="html">John&#39;s talk on CComp</title>
  <summary type="html" xml:space="preserve">
  I put John&#39;s slides for his upcoming talk on RAM compression on the website: &lt;br&gt; &lt;a target=&quot;_blank&quot; rel=nofollow href=&quot;http://www.cs.utah.edu/~coop/research/ccomp/&quot;&gt;[link]&lt;/a&gt;
  </summary>
  </entry>
  <entry>
  <author>
  <name>Nathan Cooprider</name>
  <email>c...@cs.utah.edu</email>
  </author>
  <updated>2007-04-27T19:57:48Z</updated>
  <id>http://groups.google.com/group/cxprop-users/browse_frm/thread/e41621fe9162fcd9</id>
  <link href="http://groups.google.com/group/cxprop-users/browse_frm/thread/e41621fe9162fcd9" />
  <title type="html">CIL tools for TinyOS</title>
  <summary type="html" xml:space="preserve">
  I just put together a web page which has simplified binaries and scripts &lt;br&gt; for running our static analysis tools on TinyOS code. It is designed to &lt;br&gt; help people get started easier at using our tools: &lt;br&gt; &lt;a target=&quot;_blank&quot; rel=nofollow href=&quot;http://www.cs.utah.edu/~coop/research/tools/&quot;&gt;[link]&lt;/a&gt;
  </summary>
  </entry>
  <entry>
  <author>
  <name>Nathan Cooprider</name>
  <email>c...@cs.utah.edu</email>
  </author>
  <updated>2007-04-26T21:07:13Z</updated>
  <id>http://groups.google.com/group/cxprop-users/browse_frm/thread/b59f300bd5521a0b</id>
  <link href="http://groups.google.com/group/cxprop-users/browse_frm/thread/b59f300bd5521a0b" />
  <title type="html">CComp and other updates</title>
  <summary type="html" xml:space="preserve">
  I have just expanded the CComp web page to be somewhat useful: &lt;br&gt; &lt;a target=&quot;_blank&quot; rel=nofollow href=&quot;http://www.cs.utah.edu/~coop/research/ccomp&quot;&gt;[link]&lt;/a&gt; &lt;br&gt; CComp extends cXprop to do offline compression of on-chip RAM. There is &lt;br&gt; a link on the page to our paper describing this technique. &lt;br&gt; If you haven&#39;t visited the cXprop page in a while, it is still here:
  </summary>
  </entry>
  <entry>
  <author>
  <name>Nathan Cooprider</name>
  <email>c...@cs.utah.edu</email>
  </author>
  <updated>2006-02-18T15:33:47Z</updated>
  <id>http://groups.google.com/group/cxprop-users/browse_frm/thread/71f2120af17c21c1</id>
  <link href="http://groups.google.com/group/cxprop-users/browse_frm/thread/71f2120af17c21c1" />
  <title type="html">Another test</title>
  <summary type="html" xml:space="preserve">
  Testing again.
  </summary>
  </entry>
  <entry>
  <author>
  <name>Nathan Cooprider</name>
  <email>c...@cs.utah.edu</email>
  </author>
  <updated>2005-09-14T20:38:14Z</updated>
  <id>http://groups.google.com/group/cxprop-users/browse_frm/thread/b98a1038004b6562</id>
  <link href="http://groups.google.com/group/cxprop-users/browse_frm/thread/b98a1038004b6562" />
  <title type="html">Test</title>
  <summary type="html" xml:space="preserve">
  This is a test message.
  </summary>
  </entry>
</feed>
