public inbox for gas2@sourceware.org
 help / color / mirror / Atom feed
From: Ian Lance Taylor <ian@cygnus.com>
To: hjl@lucon.org
Cc: gas2@cygnus.com, kunimart@pit.ktu.lt
Subject: Re: A PREFIX_SEPARATOR bug in binutils 2.9
Date: Tue, 21 Apr 1998 12:39:00 -0000	[thread overview]
Message-ID: <199804211939.PAA05064@subrogation.cygnus.com> (raw)
In-Reply-To: <m0yRioY-00058vC@ocean.lucon.org>

   From: hjl@lucon.org (H.J. Lu)
   Date: Tue, 21 Apr 1998 12:34:46 -0700 (PDT)

   > Why not encourage people to write the prefix on a separate line, which
   > works for both a.out and ELF?
   > 

   That is a separate issue. Since PREFIX_SEPARATOR is wrong on ELF, we
   should fix it. I think we can change it

   #define PREFIX_SEPARATOR '\\'

   so that everyone will be happy.

I am questioning the need for PREFIX_SEPERATOR at all.  I don't see
any particular reason to use it on ELF if it is not required and if no
other ELF assembler supports it.

Since changing PREFIX_SEPERATOR to a backslash won't help any existing
code, nor help any person that I know of, nor conform to any existing
documentation, I don't see any reason to do it.

I think it would make more sense to remove PREFIX_SEPERATOR entirely
from the i386 ELF assembler.  However, since the existing assembler
appears to work, and it has many far more serious coding problems,
that would be a zero priority change.

Ian

  reply	other threads:[~1998-04-21 12:39 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-04-21 11:41 H.J. Lu
1998-04-21 11:54 ` Ian Lance Taylor
1998-04-21 12:32   ` H.J. Lu
1998-04-21 12:39     ` Ian Lance Taylor
1998-04-21 12:39       ` H.J. Lu
1998-04-21 12:39         ` Ian Lance Taylor
1998-04-21 12:32           ` Martynas Kunigelis
1998-04-21 12:34             ` Ian Lance Taylor
1998-04-21 12:34           ` H.J. Lu
1998-04-21 12:39             ` Ian Lance Taylor [this message]
1998-04-21 17:45               ` Alan Modra

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=199804211939.PAA05064@subrogation.cygnus.com \
    --to=ian@cygnus.com \
    --cc=gas2@cygnus.com \
    --cc=hjl@lucon.org \
    --cc=kunimart@pit.ktu.lt \
    /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).