public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: bangerth@dealii.org
To: gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, jmortensen@cfl.rr.com,
	nobody@gcc.gnu.org
Subject: Re: c/10875: There is no multiple symbol definition error or warning for global symbols
Date: Mon, 19 May 2003 22:10:00 -0000	[thread overview]
Message-ID: <20030519221033.21396.qmail@sources.redhat.com> (raw)

Synopsis: There is no multiple symbol definition error or warning for global symbols

State-Changed-From-To: open->closed
State-Changed-By: bangerth
State-Changed-When: Mon May 19 22:10:33 2003
State-Changed-Why:
    The code is not legal, but the standard says that no
    diagnostic is required.
    
    If you want to complain anywhere, do so with the binutils
    guys. They maintain the linker. Most frequently, though,
    the answer will probably be "Don't do it". The reason
    being that the linker will usually warn you if a symbol
    has different size, but "int" and "int*" often have the
    same size, and then the linker can't really do anything
    about it.
    
    W.

http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=10875


                 reply	other threads:[~2003-05-19 22:10 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20030519221033.21396.qmail@sources.redhat.com \
    --to=bangerth@dealii.org \
    --cc=gcc-bugs@gcc.gnu.org \
    --cc=gcc-gnats@gcc.gnu.org \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=jmortensen@cfl.rr.com \
    --cc=nobody@gcc.gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).