From: Jan Hubicka <jh@suse.cz>
To: Rask Ingemann Lambertsen <rask@sygehus.dk>
Cc: Jan Hubicka <jh@suse.cz>, Uros Bizjak <ubizjak@gmail.com>,
GCC Patches <gcc-patches@gcc.gnu.org>,
Richard Kenner <kenner@vlsi1.ultra.nyu.edu>,
rridge@csclub.uwaterloo.ca
Subject: Re: New back end ia16: 16-bit Intel x86
Date: Thu, 09 Aug 2007 09:33:00 -0000 [thread overview]
Message-ID: <20070809093309.GT20007@kam.mff.cuni.cz> (raw)
In-Reply-To: <20070808185154.GE25795@sygehus.dk>
>
> Looking at the few people who have commented on the issue, I notice that
> among those who are not i386 maintainers, 100 % are in favour of a merge.
> Among the i386 maintainers, 50 % are in favour and 50 % are against. I'll be
> working on the 16-bit x86 code and is also against it.
Well, given that there seems to be mostly consensus about merging the
backend, I guess it is way to go. If you are interested to do the job, I
will be happy to review the incremental patches (at least till 22nd when
I am leaving for 8 days).
I would propose the plan of getting initial changes into mainline before
stage2 closes and continuing on the branch. Definitly the changes for
branch can be reviewed making merge at stage1 easy.
>
> > > >1a) ix86_fixup_binary_operands() / ia16_prepare_operands()
> > > >1b) ix86_binary_operator_ok() / ia16_arith_operands_p()
> > > >2a) ix86_cc_mode() / ia16_select_cc_mode()
> > > >2b) ix86_cc_modes_compatible() / ia16_cc_modes_compatible()
> > > >2c) ix86_expand_carry_flag_compare() looks interesting.
> > > >2d) ix86_expand_int_movcc() too, but I'd rather fix/extend if-conversion.
> > > >3a) PLUS/MINUS patterns which make use of the carry flag. For example the
> > > >ones I have proposed for fixing PR target/30315.
> > > >3b) Multiword PLUS/MINUS where both have room for improvement when it comes
> > > >to using the condition codes and i386 could use updating for lower-subreg.
> > > >4) x87 instructions.
> >
> > I would a lot preffer full sharing of i386 backend over sharing just
> > couple of functions as suggested above. Many of those have not terribly
> > well defined semantics and depends a lot on i386 backend internals.
>
> It is possible to define and document semantics. In many cases, it is
> even thought of as a good idea.
We would have to stabilize fair amount of i386 internal interfaces (ie
pattern names for various instructions, macros defined and such) to get
the common expanders working. This does not seem terribly practical
even if it is certainly doable.
Honza
>
> --
> Rask Ingemann Lambertsen
next prev parent reply other threads:[~2007-08-09 9:33 UTC|newest]
Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-06 14:23 Uros Bizjak
2007-08-07 1:29 ` Rask Ingemann Lambertsen
2007-08-07 17:37 ` Daniel Jacobowitz
2007-08-07 20:03 ` Uros Bizjak
2007-08-08 12:21 ` Jan Hubicka
2007-08-08 17:30 ` Mark Mitchell
2007-08-08 23:22 ` Richard Kenner
2007-08-08 18:52 ` Rask Ingemann Lambertsen
2007-08-08 20:24 ` Michael Matz
2007-08-08 20:59 ` H.J. Lu
2007-08-08 22:46 ` DJ Delorie
2007-08-09 9:33 ` Jan Hubicka [this message]
2007-08-09 14:01 ` Rask Ingemann Lambertsen
2007-08-09 15:43 ` DJ Delorie
2007-08-08 15:28 ` Rask Ingemann Lambertsen
2007-08-17 22:38 ` H. Peter Anvin
2007-08-18 2:34 ` Rask Ingemann Lambertsen
2007-08-18 5:33 ` H. Peter Anvin
2007-08-18 17:36 ` Rask Ingemann Lambertsen
2007-08-18 17:50 ` H. Peter Anvin
2007-08-18 20:39 ` Rask Ingemann Lambertsen
2007-08-19 2:11 ` H. Peter Anvin
2007-08-19 12:25 ` Rask Ingemann Lambertsen
2007-08-19 20:07 ` H. Peter Anvin
2007-08-21 8:48 ` H. Peter Anvin
2007-08-21 14:35 ` Rask Ingemann Lambertsen
2007-08-21 17:46 ` H. Peter Anvin
2007-08-21 18:56 ` Real-mode i386 back end (Was: New back end ia16: 16-bit Intel x86) Rask Ingemann Lambertsen
2007-08-19 7:29 ` New back end ia16: 16-bit Intel x86 H. Peter Anvin
2007-08-19 10:56 ` Rask Ingemann Lambertsen
2007-08-19 21:40 ` H. Peter Anvin
-- strict thread matches above, loose matches on Subject: below --
2007-08-19 19:58 Ross Ridge
2007-08-19 16:11 Ross Ridge
2007-08-19 17:36 ` Rask Ingemann Lambertsen
2007-08-18 20:46 Ross Ridge
2007-08-19 16:20 ` Rask Ingemann Lambertsen
2007-08-02 20:15 Ross Ridge
2007-08-01 19:25 Ross Ridge
2007-08-01 22:57 ` Rask Ingemann Lambertsen
[not found] <20070801153758.ACBB974253@caffeine.csclub.uwaterloo.ca.suse.lists.egcs-patches>
2007-08-01 17:44 ` Andi Kleen
2007-08-01 15:38 Ross Ridge
2007-08-01 17:59 ` Rask Ingemann Lambertsen
2007-07-31 18:06 Ross Ridge
2007-08-01 0:34 ` Rask Ingemann Lambertsen
2007-08-01 9:53 ` Richard Kenner
2007-08-01 12:33 ` Rask Ingemann Lambertsen
2007-08-01 12:44 ` Richard Kenner
2007-08-01 13:41 ` Rask Ingemann Lambertsen
2007-08-01 13:52 ` Richard Kenner
2007-08-01 10:38 ` Jan Hubicka
2007-08-01 17:30 ` Rask Ingemann Lambertsen
2007-07-31 15:24 Ross Ridge
2007-07-31 17:44 ` Michael Matz
2007-07-31 0:50 Ross Ridge
2007-07-31 8:54 ` Tristan Gingold
2007-07-31 13:46 ` Rask Ingemann Lambertsen
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=20070809093309.GT20007@kam.mff.cuni.cz \
--to=jh@suse.cz \
--cc=gcc-patches@gcc.gnu.org \
--cc=kenner@vlsi1.ultra.nyu.edu \
--cc=rask@sygehus.dk \
--cc=rridge@csclub.uwaterloo.ca \
--cc=ubizjak@gmail.com \
/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).