From: Jim Wilson <wilson@chestnut.cygnus.com>
To: Ruediger Helsch <rh@unifix.de>
Cc: Jim Wilson <wilson@cygnus.com>, Ian Lance Taylor <ian@cygnus.com>,
rms@gnu.ai.mit.edu, drepper@cygnus.com, dm@sgi.com,
gcc2@cygnus.com, gas2@cygnus.com
Subject: Re: global vars and symbol visibility for mips32/elf
Date: Tue, 13 Aug 1996 19:04:00 -0000 [thread overview]
Message-ID: <199608140204.TAA12591@cygnus.com> (raw)
In-Reply-To: <Pine.LNX.3.91.960813235516.19616B-100000@anna.unifix.de>
#include <assert.h>
int optind[30000], optarg[30000];
...
This is a good example. A number of systems get this wrong. One way to fix
this is to make -fno-common the default. However, ANSI/ISO C does not require
this solution. There are some other ways that this problem could be solved,
by changing how the C library works, or by changing how the linker works.
-fno-common is probably the easiest solution though.
Jim
next prev parent reply other threads:[~1996-08-13 19:04 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 [this message]
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
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=199608140204.TAA12591@cygnus.com \
--to=wilson@chestnut.cygnus.com \
--cc=dm@sgi.com \
--cc=drepper@cygnus.com \
--cc=gas2@cygnus.com \
--cc=gcc2@cygnus.com \
--cc=ian@cygnus.com \
--cc=rh@unifix.de \
--cc=rms@gnu.ai.mit.edu \
--cc=wilson@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).