public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Jeffrey A Law <law@cygnus.com>
To: "Jerry Quinn" <jquinn@nortelnetworks.com>
Cc: binutils@sourceware.cygnus.com
Subject: Re: Patch: add prefix to condition args in opcodes
Date: Thu, 05 Aug 1999 14:41:00 -0000	[thread overview]
Message-ID: <23158.933888941@upchuck.cygnus.com> (raw)
In-Reply-To: <14239.3863.98454.352088@gargle.gargle.HOWL>

  In message <14239.3863.98454.352088@gargle.gargle.HOWL>you write:
  > Sorry.  I was thinking they were close enough, but you're right.  They are
  > independent.
It happens.  Often I can extract the pieces, but my time is very limited right
now, so I have to ask others to extract the independent pieces.


  > I think we should also do the completers and float regs once you're happy
  > with this change.
I think so too.  Hopefully that'll give us enough letters to finish the PA2.0
work and maybe, just maybe clean up the code a little in the process.

One of the big issues at hand was whether or not to completely revamp the
entire PA assembler when we added PA2.0 support.  I wanted to do that, but
simply didn't have the time.  So, we're stuck trying to make the current
mess of spaghetti code work and trying to clean up pieces as we go along.

  >  > The flow control (at least to me) is easier to follow with that kind of 
  > style
  >  > (it's still not ideal, but I'm not sure what else we can do to clean thi
  > s up
  >  > without starting over with a complete redesign).
  > 
  > I saw that construction and I had thought what I did was preferable
  > because it avoided a redundant test.  If you think it's better to write
  > it that way, I'll change it.
I prefer code that's easier to read/follow over code that avoids a comparison.
Particularly in this case since assembly time is usually dwarfed by the compile
time.

  > Welcome back.  Glad to see you now have a chance to breathe :-)
Breathe?  No way, I barely get time to blink :-)

jeff

WARNING: multiple messages have this Message-ID
From: Jeffrey A Law <law@cygnus.com>
To: "Jerry Quinn" <jquinn@nortelnetworks.com>
Cc: binutils@sourceware.cygnus.com
Subject: Re: Patch: add prefix to condition args in opcodes
Date: Thu, 05 Aug 1999 14:41:00 -0000	[thread overview]
Message-ID: <23158.933888941@upchuck.cygnus.com> (raw)
Message-ID: <19990805144100.V6NjoBnw23PbB7dI8G-aTMoVQN8krvjq5HkGF2NkJfw@z> (raw)
In-Reply-To: <14239.3863.98454.352088@gargle.gargle.HOWL>

  In message < 14239.3863.98454.352088@gargle.gargle.HOWL >you write:
  > Sorry.  I was thinking they were close enough, but you're right.  They are
  > independent.
It happens.  Often I can extract the pieces, but my time is very limited right
now, so I have to ask others to extract the independent pieces.


  > I think we should also do the completers and float regs once you're happy
  > with this change.
I think so too.  Hopefully that'll give us enough letters to finish the PA2.0
work and maybe, just maybe clean up the code a little in the process.

One of the big issues at hand was whether or not to completely revamp the
entire PA assembler when we added PA2.0 support.  I wanted to do that, but
simply didn't have the time.  So, we're stuck trying to make the current
mess of spaghetti code work and trying to clean up pieces as we go along.

  >  > The flow control (at least to me) is easier to follow with that kind of 
  > style
  >  > (it's still not ideal, but I'm not sure what else we can do to clean thi
  > s up
  >  > without starting over with a complete redesign).
  > 
  > I saw that construction and I had thought what I did was preferable
  > because it avoided a redundant test.  If you think it's better to write
  > it that way, I'll change it.
I prefer code that's easier to read/follow over code that avoids a comparison.
Particularly in this case since assembly time is usually dwarfed by the compile
time.

  > Welcome back.  Glad to see you now have a chance to breathe :-)
Breathe?  No way, I barely get time to blink :-)

jeff

  reply	other threads:[~1999-08-05 14:41 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <199907092055.NAA11875@cygnus.com>
1999-07-28  3:19 ` Jeffrey A Law
1999-07-28  7:11   ` Jerry Quinn
1999-08-05 14:41     ` Jeffrey A Law [this message]
1999-08-05 14:41       ` Jeffrey A Law
1999-07-28 10:12   ` Jerry Quinn
1999-08-05 16:02     ` Jeffrey A Law
1999-08-05 16:02       ` Jeffrey A Law
     [not found] <65154398@toto.iv>
1999-07-12 13:17 ` Jerry Quinn
1999-07-09 13:53 Jerry Quinn

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=23158.933888941@upchuck.cygnus.com \
    --to=law@cygnus.com \
    --cc=binutils@sourceware.cygnus.com \
    --cc=jquinn@nortelnetworks.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).