linux-sparse.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Christopher Li <sparse@chrisli.org>
To: Kamil Dudka <kdudka@redhat.com>, Jeff Garzik <jeff@garzik.org>
Cc: Sparse Mailing-list <linux-sparse@vger.kernel.org>
Subject: Re: [PATCH] compile-i386: do not generate an infinite loop
Date: Wed, 22 Jul 2009 01:38:43 -0700	[thread overview]
Message-ID: <70318cbf0907220138g412388fam12f31f03c25ebf1f@mail.gmail.com> (raw)
In-Reply-To: <200907182334.10900.kdudka@redhat.com>

On Sat, Jul 18, 2009 at 2:34 PM, Kamil Dudka<kdudka@redhat.com> wrote:
> Hello,
>
> I've probably encountered a bug within compile-i386.c. It generates
> an infinite loop for 'while' statement. My testing example and proposed
> patch are enclosed.

Adding Jeff to the CC list. The compile-i386.c is Jeff's pet project.
The change looks good to me. I would like to give Jeff some time
to comment it before I apply the patch.

BTW, have you take a look at Linus's example.c? It is based on the
linearized byte code and It does more advance stuff like simple
register allocation. In my opinion example.c is a better place to start
hacking compiler back end  than compile.c

Chris

  reply	other threads:[~2009-07-22  8:38 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-18 21:34 [PATCH] compile-i386: do not generate an infinite loop Kamil Dudka
2009-07-22  8:38 ` Christopher Li [this message]
2009-07-22  9:24   ` Kamil Dudka
2009-07-22 16:34     ` Christopher Li
2009-07-22 17:21       ` Kamil Dudka
2009-07-22 19:30         ` Christopher Li
2009-07-22 12:45   ` Jeff Garzik
2009-07-22 16:39 ` Christopher Li
2009-07-22 16:51   ` Jeff Garzik
2009-07-22 17:02     ` Kamil Dudka
2009-07-22 19:18     ` Christopher Li

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=70318cbf0907220138g412388fam12f31f03c25ebf1f@mail.gmail.com \
    --to=sparse@chrisli.org \
    --cc=jeff@garzik.org \
    --cc=kdudka@redhat.com \
    --cc=linux-sparse@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).