9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Latchesar Ionkov <lucho@ionkov.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] 8a/8l bug
Date: Wed, 17 Dec 2003 19:13:13 -0500	[thread overview]
Message-ID: <20031218001313.GA8411@ionkov.net> (raw)
In-Reply-To: <E1AWlFI-000BDN-To@t40.swtch.com>

On Wed, Dec 17, 2003 at 06:38:22PM -0500, Russ Cox said:
> > 1. Adds a new option whether to do instruction optimizations.
> > 2. Modifies y* arrays to have a flag whether the instruction code should be
> > used if the optimizations are on.
>
> I don't want a flag to fix broken behavior.
> I want the linker to do the right thing.
>
> I'd rather change the linker just to drop the
> INCL/DECL as possible ADDL/SUBL encodings
> and then change the compiler if the hit is actually
> significant (seems like it could be).
>
> How many other instructions are affected?
>
> > 3. Optionally the flag also holds information whether the specific
> > instruction has 0x0f/0x66 headers overriding the default specified in the
> > optab array.
>
> If you need this to handle certain instructions, then this seems
> reasonable, although I'm not sure I understand why it can't
> be handled with just a separate line in the y* array.

The flag if there should be 0x0f or 0x66 header is defined per opcode (Pm,
Pe) in optab instead of being defined per line in y*.

I already changed the machine description in gcc to avoid the problem, so I
don't need it badly, but gcc generates suboptimal code now.

BTW currently gcc compiles and executes correctly about 95% of the testcases
for C that come with it. Currently I am using gcc hosted in Linux. It uses
8a and 8l to generate the executables. When I get 98% of the testcases
correctly, I'll try C++.


  reply	other threads:[~2003-12-18  0:13 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-17 17:59 Latchesar Ionkov
2003-12-17 19:26 ` Latchesar Ionkov
2003-12-17 22:54   ` Russ Cox
2003-12-17 23:33     ` Latchesar Ionkov
2003-12-17 23:38       ` Russ Cox
2003-12-18  0:13         ` Latchesar Ionkov [this message]
2003-12-18  0:25         ` Charles Forsyth
2003-12-18  4:54   ` jmk

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=20031218001313.GA8411@ionkov.net \
    --to=lucho@ionkov.net \
    --cc=9fans@cse.psu.edu \
    /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).