From: David Mosberger <davidm@napali.hpl.hp.com>
To: linux-ia64@vger.kernel.org
Subject: RE: [Linux-ia64] [Patch] trivial fix in linker script
Date: Wed, 29 Jan 2003 19:15:59 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590709805773@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590709805734@msgid-missing>
>>>>> On Wed, 29 Jan 2003 10:30:52 -0800, "Siddha, Suresh B" <suresh.b.siddha@intel.com> said:
Suresh> I am using GNU linker.
I see.
Suresh> Inline with your observation, Intel compiler emits the type
Suresh> of extern variables. And now based on the order in which
Suresh> object files are linked, linker is failing in some cases.
Suresh> If the object file with extern declaration comes after the
Suresh> object file with correct declaration, linker is working
Suresh> fine. But if the object file with extern declaration comes
Suresh> first, then linker is reporting "type of symbol changed" in
Suresh> the second object file with correct declaration.
Huh, and this is a fatal error, not a warning?
Suresh> gcc doesn't fix the type for extern variables, leaves it to
Suresh> the linker. So linking works irrespective of the order.
Suresh> Is this a GNU linker issue?
Perhaps. We might want to discuss it with Richard Henderson.
Currently the GNU linker is a bit overzealous in enforcing certain
restrictions anyhow, which make it a pain for the linux kernel (e.g.,
it doesn't allow the mixing of CONST_GP and non-CONST_GP files, even
if the non-CONST_GP files contain only data, etc.). Perhaps it's just
time to clean up the toolchain in this regard.
Don't get me wrong: I can live with the linker script magic if the
toolchain folks argue that it is the proper way to handle this. I
just want to avoid uglifying the kernel for no good reason.
--david
prev parent reply other threads:[~2003-01-29 19:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-21 3:16 [Linux-ia64] [Patch] trivial fix in linker script Siddha, Suresh B
2003-01-24 18:30 ` David Mosberger
2003-01-24 20:05 ` Siddha, Suresh B
2003-01-28 19:14 ` David Mosberger
2003-01-28 19:29 ` Sam Ravnborg
2003-01-29 18:30 ` Siddha, Suresh B
2003-01-29 19:15 ` David Mosberger [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=marc-linux-ia64-105590709805773@msgid-missing \
--to=davidm@napali.hpl.hp.com \
--cc=linux-ia64@vger.kernel.org \
/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