public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Jakub Jelinek <jakub@redhat.com>
To: Nick Clifton <nickc@redhat.com>
Cc: Simon Burge <simonb@wasabisystems.com>,
	Ian Lance Taylor <ian@airs.com>,
	binutils@sources.redhat.com
Subject: Re: .eh_frame section on alpha
Date: Tue, 04 Jan 2005 09:58:00 -0000	[thread overview]
Message-ID: <20050104095809.GQ3168@sunsite.mff.cuni.cz> (raw)
In-Reply-To: <41DA653D.6030101@redhat.com>

On Tue, Jan 04, 2005 at 09:43:25AM +0000, Nick Clifton wrote:
> Hi Simon,
> 
> >>However, I also think it would be a good idea to have an assembler
> >>option to not create the unwind information.
> 
> >Strongly agreed :-)  I can come up with a patch, but I'm not sure what a
> >good option name would be.  --no-auto-eh-frame seems a little unwieldy.
> 
> How about: --no-create-eh-frame ?
> 
> I see no problem with long switch names.  It is better that they are 
> expressive and tell the user what they are doing.  Shorter, more compact 
> switch names are often confusing and can lead to user misunderstanding.

Can't this be done already without adding new options with a
/DISCARD/ : { *(.eh_frame) }
in the linker script?

	Jakub

  reply	other threads:[~2005-01-04  9:58 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-24 13:22 Simon Burge
2004-12-24 15:00 ` Ian Lance Taylor
2004-12-29  7:39   ` Simon Burge
2005-01-04  9:36     ` Nick Clifton
2005-01-04  9:58       ` Jakub Jelinek [this message]
2005-01-04 10:06         ` Nick Clifton
2005-01-04 17:51           ` Richard Henderson
2005-01-04 21:27             ` Simon Burge
2005-01-04 22:40               ` Jakub Jelinek
2005-01-05  2:17                 ` Simon Burge
2005-01-05  3:14                   ` Richard Henderson

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=20050104095809.GQ3168@sunsite.mff.cuni.cz \
    --to=jakub@redhat.com \
    --cc=binutils@sources.redhat.com \
    --cc=ian@airs.com \
    --cc=nickc@redhat.com \
    --cc=simonb@wasabisystems.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).