From: Steven Bosscher <s.bosscher@student.tudelft.nl>
To: "gcc@gcc.gnu.org" <gcc@gcc.gnu.org>
Subject: Why are BLOCK_HEAD/BLOCK_END not used?
Date: Mon, 08 Dec 2003 15:33:00 -0000 [thread overview]
Message-ID: <200312081630.14467.s.bosscher@student.tudelft.nl> (raw)
Hello,
For tree-ssa I would like to make the basic block head/end a union because we
now have a head and end for both RTL and trees, and obviously we only can use
one at a time so one field at least is redundant.
Problem is, everything uses bb->head instead of BLOCK_HEAD (bb), and bb->end
instead of BLOCK_END (bb). Is there a reason for this? Would a patch to
update _all_ of these to use the macro be acceptable in stage3 if it prevents
merge trouble for the tree-ssa branch maintainers?
Gr.
Steven
next reply other threads:[~2003-12-08 15:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-08 15:33 Steven Bosscher [this message]
2003-12-08 22:09 ` [RFC] Use accessor macros for the head and end of a basic block Steven Bosscher
2003-12-08 22:35 ` Jan Hubicka
2003-12-09 5:04 ` law
2003-12-09 6:52 ` Steven Bosscher
2003-12-09 9:28 ` law
2003-12-10 8:47 ` Steven Bosscher
2003-12-10 22:49 ` Zack Weinberg
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=200312081630.14467.s.bosscher@student.tudelft.nl \
--to=s.bosscher@student.tudelft.nl \
--cc=gcc@gcc.gnu.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).