From: "Alexander Aganichev" <AAganichev@hypercom.com>
To: binutils@sourceware.cygnus.com
Subject: IEEE support issues
Date: Sat, 01 Jul 2000 01:17:00 -0000 [thread overview]
Message-ID: <OF30CFFD2E.898E5C71-ONC325690F.002B674C@hypercom.com> (raw)
Hi!
1. This code in ieee.c was fixed in CVS but then reverted:
==
info->filename = filename;
modname = strrchr (filename, '/');
/* We could have a mixed forward/back slash case. */
backslash = strrchr (modname, '\\');
if (backslash > modname)
modname = backslash;
if (modname != NULL)
++modname;
==
Could anyone please to replace at least `modname' with `filename' in the
second strrchr so binutils will not crash on IEEE producing? I really don't
care about signed pointers but this change is essential for me since we
regularly produce IEEE object files from COFF in our company ;-)
2. The second issue I found is that GCC and Binutils differently parses
size in .stab debug information: GCC produces sizes in bits and Binutils
assumes bytes. I don't know who is right (though it seems like GCC) but
this issue should be resolved. Currently I've added division by 8 to the
parse_stab_type() (stabs.c) as follows:
==
switch (*attr)
{
case 's':
size = atoi (attr + 1) / 8; /* adjust the size */
if (size <= 0)
size = -1;
break;
case 'S':
stringp = true;
break;
default:
/* Ignore unrecognized type attributes, so future
compilers can invent new ones. */
break;
}
==
--
Alexander Aganichev
Hypercom Europe Limited, Inc.
Software Engineer
next reply other threads:[~2000-07-01 1:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-07-01 1:17 Alexander Aganichev [this message]
2000-07-01 3:00 ` Alan Modra
2000-07-01 3:16 ` Where should gcc-avr info files go? Russ.Shaw
2000-07-02 22:29 IEEE support issues Alexander Aganichev
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=OF30CFFD2E.898E5C71-ONC325690F.002B674C@hypercom.com \
--to=aaganichev@hypercom.com \
--cc=binutils@sourceware.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).