From: Doug Evans <dje@sebabeach.org>
To: cgen@sourceware.org
Subject: s-parallel cleanup, better error messages for rtl evaluation
Date: Fri, 25 Sep 2009 19:53:00 -0000 [thread overview]
Message-ID: <20090925195337.425F36E3D9@sebabeach.org> (raw)
Hi.
fyi, I just checked this in.
[tested with m32r sim, all sid sims, all opcodes ports, no
changes in output]
It fixes code generation for parallels (e.g. `if' inside parallel
is now supported) by doing a proper traversal of the rtx.
[I don't think this is the final word though.
But in normal form I'm approaching this incrementally,
I certainly haven't made things worse.]
It also improves the error message during, for example, c code
generation by including the pretty-printed outer expression.
[It's not finished though, xops aren't printed in a user-friendly form.
That'll come in a later patch.]
2009-09-25 Doug Evans <dje@sebabeach.org>
* operand.scm (/anyof-merge-setter): Handle set-quiet.
* rtl.scm (rtx-single-set?): Handle set-quiet.
* rtl-c.scm (estate-make-for-rtl-c): Delete args context, owner,
rtl-cover-fns?, macro?. All callers updated.
(estate-make-for-normal-rtl-c): Delete, have all callers call
estate-make-for-rtl-c directly.
(rtl-c-parsed): Pass #:outer-expr to estate-make-for-rtl-c.
(rtl-c, rtl-c-expr-parsed, rtl-c-expr, rtl-c++-parsed, rtl-c++): Ditto.
* rtl-c.scm (/par-replace-set-dest-expr-fn): New function,
replaces /par-replace-set-dests.
(/par-replace-set-src-expr-fn): New function, replaces
/par-replace-set-srcs.
(s-parallel): Rewrite.
* rtl.scm (rtx-pretty-strdump): New function.
* rtl-traverse.scm (/rtx-canon-error): Use it.
(<eval-state>): New member outer-expr.
(estate-error): Include outer expression in error message if present.
reply other threads:[~2009-09-25 19:53 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20090925195337.425F36E3D9@sebabeach.org \
--to=dje@sebabeach.org \
--cc=cgen@sourceware.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 read-only IMAP folder(s) and NNTP newsgroup(s).