From: Minh Tran-Le <TRANLE@intellicorp.com>
To: ian@cygnus.com
Cc: gas2@cygnus.com
Subject: Re: problem with ld (i386-coff) leaving holes in the
Date: Tue, 09 Aug 1994 14:11:00 -0000 [thread overview]
Message-ID: <199408092045.AA17786@bridge2.NSD.3Com.COM> (raw)
In-Reply-To: <199408091358.JAA03258@sanguine.cygnus.com>
|Ian Lance Taylor <ian@cygnus.com> wrote:
|
| Date: Mon, 8 Aug 94 19:47:36 PDT
| From: Minh Tran-Le <TRANLE@intellicorp.com>
|
| I made ld printout the section name and flags in the case it wants to
| page align it.
|
| section .text: flags 0x237
| section .data: flags 0x247
| section .comment: flags 0x10203
| section .lib: flags 0x203
|
|Can you find out what SEC_LOAD and SEC_ALLOC are set for all the
|sections? I don't see why they should be set for .comment or .lib.
Well looking at the function styp_to_sec_flags in coffcode.h it seems
that it is setting the section flags to SEC_LOAD|SEC_ALLOC (line 462)
for all styp_flags that it does not know about.
For i386-aix, the .comment sections have either an styp of either
0x0 or 0x200 and the .lib sections have an styp of 0x800. So the
function stype_to_sec_load will return for some of the .comment
sections and all the .lib the value 0x3 which is SEC_LOAD|SEC_ALLOC.
Maybe the function styp_to_sec_flags should not set the default
section flags to SEC_LOAD|SEC_ALLOC.
Minh Tran-Le.
-------
next prev parent reply other threads:[~1994-08-09 14:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
1994-08-07 10:59 problem with ld (i386-coff) leaving holes in the executable Minh Tran-Le
1994-08-08 7:59 ` Ian Lance Taylor
1994-08-08 20:11 ` problem with ld (i386-coff) leaving holes in the Minh Tran-Le
1994-08-09 6:58 ` Ian Lance Taylor
1994-08-09 14:11 ` Minh Tran-Le [this message]
1994-08-10 10:03 ` Ian Lance Taylor
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=199408092045.AA17786@bridge2.NSD.3Com.COM \
--to=tranle@intellicorp.com \
--cc=gas2@cygnus.com \
--cc=ian@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).