From: Ruediger Helsch <rh@unifix.de>
To: dm@sgi.com
Cc: gcc2@cygnus.com, gas2@cygnus.com
Subject: Re: global vars and symbol visibility for mips32/elf
Date: Tue, 13 Aug 1996 09:06:00 -0000 [thread overview]
Message-ID: <Pine.LNX.3.91.960813170639.26776G-100000@anna.unifix.de> (raw)
In-Reply-To: <199608090946.CAA27226@neteng.engr.sgi.com>
On Fri, 9 Aug 1996, David S. Miller wrote:
> The problem is caused by the symbol 'glob'. GNU libc also has a
> symbol glob. The assembly output by gcc for the glob variable in the
> 960218-1.c test case looks like:
This is a combination of several bugs:
1) ANSI C compilers do not know COMMON, they should generate a data
definition for glob (ISO/IEC 9899:1990 6.7.2). Gcc generates a
COMMON even with -ansi (there is a comment in the code indicating
this standard violation is on purpose).
2) The linker should not link a common against a function from the
shared library.
Both bugs are since nearly one year fixed in Unifix Linux and Linux-FT
(POSIX certified).
Ruediger Helsch <rh@unifix.de>
next prev parent reply other threads:[~1996-08-13 9:06 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
1996-08-09 2:46 David S. Miller
1996-08-09 5:24 ` David S. Miller
1996-08-09 9:01 ` Ian Lance Taylor
1996-08-09 8:30 ` Ian Lance Taylor
1996-08-09 13:13 ` Ulrich Drepper
1996-08-09 15:30 ` Ian Lance Taylor
1996-08-10 17:37 ` Richard Stallman
1996-08-10 19:41 ` Ian Lance Taylor
1996-08-10 23:26 ` Jim Wilson
1996-08-11 1:44 ` Richard Stallman
1996-08-13 10:58 ` Ruediger Helsch
1996-08-13 13:36 ` Jim Wilson
1996-08-13 16:06 ` Ruediger Helsch
1996-08-13 19:04 ` Jim Wilson
1996-08-13 21:02 ` Richard Stallman
1996-08-14 3:06 ` Ruediger Helsch
1996-08-14 23:44 ` Richard Stallman
1996-08-14 0:18 ` Nick Ing-Simmons
1996-08-14 3:06 ` Ruediger Helsch
1996-08-15 11:24 ` H.J. Lu
1996-08-13 9:06 ` Ruediger Helsch [this message]
1996-08-13 10:58 ` Richard Stallman
1996-08-13 13:36 ` Ruediger Helsch
1996-08-13 13:36 ` Richard Stallman
1996-08-13 14:40 ` H.J. Lu
1996-08-13 16:06 ` Ulrich Drepper
1996-08-13 16:06 ` Joe Buck
1996-08-13 17:02 ` Rohan LENARD
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=Pine.LNX.3.91.960813170639.26776G-100000@anna.unifix.de \
--to=rh@unifix.de \
--cc=dm@sgi.com \
--cc=gas2@cygnus.com \
--cc=gcc2@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).