public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Quentin Neill <quentin.neill.gnu@gmail.com>
To: "H.J. Lu" <hjl.tools@gmail.com>
Cc: Jeff Law <law@redhat.com>, binutils@sourceware.org, gcc@gcc.gnu.org
Subject: Re: Scheduling x86 dispatch windows
Date: Fri, 11 Jun 2010 23:36:00 -0000	[thread overview]
Message-ID: <AANLkTilsVYghaBB1dwuaFT4gHi99SfEG2hiwBD6-mSSo@mail.gmail.com> (raw)
In-Reply-To: <AANLkTimteGwx6Amus4SodLsfKaz56v80N-aJzUmWCB9u@mail.gmail.com>

On Thu, Jun 10, 2010 at 5:23 PM, H.J. Lu <hjl.tools@gmail.com> wrote:
> [snip]
> x86 assembler isn't an optimizing assembler. -mtune only does
> instruction selection.  What you are proposing sounds like an optimizing
> assembler to me. Are we going to support scheduling, macro, ...?
> --
> H.J.

Just to clarify, we are not doing scheduling or macros.   The
assembler already supported alignment and padding using .align and
friends, which can be from the compiler and from hand-written
assembly.

Now we are seeing more complex alignment rules that are not as simple
as it used to be for the older hardware.  It will be almost impossible
for an assembly programmer to insert the right directives, not to
mention any change might invalidate previous alignments.   Assembly
programmers will be out of luck (that is, unless the compiler becomes
the assembler).

The essence is we want to insert prefixes (as well as nops) according
to certain rules known at encoding time.  The mechanism implementing
these rules can be abstracted (table driven?) and could be applicable
to any hardware having similar features.

As gcc does not currently encode and/or generate object code, we are
wary of introducing such assembler functionality and want to avoid if
possible, instead leveraging the existing binutils infrastructure.

-- 
Quentin Neill (with some input from Reza Yazdani)

  reply	other threads:[~2010-06-11 22:42 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-10 17:24 reza yazdani
2010-06-10 19:52 ` Quentin Neill
2010-06-10 20:12   ` H.J. Lu
2010-06-10 20:25     ` Jeff Law
2010-06-10 20:38       ` Joern Rennecke
2010-06-10 21:54       ` Quentin Neill
2010-06-10 22:09         ` H.J. Lu
2010-06-10 22:40           ` Quentin Neill
2010-06-10 22:48             ` H.J. Lu
2010-06-11 23:36               ` Quentin Neill [this message]
2010-06-12 18:54                 ` H.J. Lu
2010-06-13 21:54                   ` H.J. Lu
2010-06-14 13:37                     ` Michael Matz
2010-06-14 16:06                       ` Jakub Jelinek
2010-06-11  0:44       ` Daniel Jacobowitz
2010-06-11  5:58         ` Quentin Neill
2010-06-11 16:46           ` Daniel Jacobowitz
2010-06-11 19:21             ` Quentin Neill
2010-06-11 19:41               ` H.J. Lu
2010-06-11 19:50               ` Jakub Jelinek
2010-06-12 11:25               ` Andi Kleen
2010-06-12 22:45                 ` Ian Lance Taylor
2010-06-13 12:35                   ` Andi Kleen
2010-06-13 13:09                     ` Joern Rennecke
2010-06-13 14:36                       ` Andi Kleen
2010-06-13 15:02                         ` Joern Rennecke
2010-06-13 19:56                           ` Chris Lattner
2010-06-13 16:28                         ` Frank Ch. Eigler

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=AANLkTilsVYghaBB1dwuaFT4gHi99SfEG2hiwBD6-mSSo@mail.gmail.com \
    --to=quentin.neill.gnu@gmail.com \
    --cc=binutils@sourceware.org \
    --cc=gcc@gcc.gnu.org \
    --cc=hjl.tools@gmail.com \
    --cc=law@redhat.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).