From: Ian Lance Taylor <ian@cygnus.com>
To: don@pixsci.com
Cc: gas2@cygnus.com
Subject: Re: Patch for binutils (GAS-980329) for VxWorks on MIPS
Date: Mon, 30 Mar 1998 08:34:00 -0000 [thread overview]
Message-ID: <199803301634.LAA23997@subrogation.cygnus.com> (raw)
In-Reply-To: <3521B963898BD111AA6A006008A84516079B37@SERVER>
From: Don Bowman <don@pixsci.com>
Date: Sun, 29 Mar 1998 18:46:03 -0500
Under VxWorks 5.3.1 [The Tornado 1.0.1 release] for the MIPS targets,
gas cannot create a debuggable image. This occurs since the Tornado
target server requires a separate .stab & .stabstr section. It cannot
deal with the .mdebug ecoff section.
The fix is to three main areas:
1: configure: accept 'mips-wrs-vxworks' as a valid configuration target
2: obj-elf.h: allow output to separate sections. The comment that was
there indicated this had been removed due to an Irix 6 limitation. This
may not affect any of the other ELF targets, but I cannot say for
certain:
it certainly does not affect the VxWorks MIPS platform.
The .mdebug section is required on Irix 5, because the Irix 5 linker
can not handle .stab/.stabstr sections. I do not believe the .mdebug
section is required on Irix 6, although gas doesn't support Irix 6
anyhow so I haven't tested this.
It appears that your patch will always generate .stab/.stabstr
sections, even on Irix 5, since MIPS_STABS_ELF is always defined in
obj-elf.h in your patch.
Presumably WRS ships a toolchain which permits debugging for MIPS
targets. What do they do?
3: A fix to ecoff.c: the comment about input_line_pointer pointing to the
beginning of the stab value appears incorrect.
This appears unrelated to the other issues. Can you send a test case
for this? As far as I can tell from s_stab_generic,
input_line_pointer will indeed point to the start of the value when
ecoff_stab is called. Without a test case, I can't judge whether your
patch is appropriate.
Ian
prev parent reply other threads:[~1998-03-30 8:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-03-29 15:46 Don Bowman
1998-03-30 8:34 ` Ian Lance Taylor [this message]
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=199803301634.LAA23997@subrogation.cygnus.com \
--to=ian@cygnus.com \
--cc=don@pixsci.com \
--cc=gas2@cygnus.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).