From: Roland McGrath <roland@gnu.ai.mit.edu>
To: ian@cygnus.com
Cc: Robert.Wilhelm@physik.tu-muenchen.de, hjl@innovix.com,
gcc2@cygnus.com, raeburn@cygnus.com, gas2@cygnus.com,
rwilhelm@physik.tu-muenchen.de
Subject: Re: Bugs in gcc or binutils 2.7?
Date: Thu, 18 Jul 1996 13:25:00 -0000 [thread overview]
Message-ID: <199607182024.QAA11657@delasyd.gnu.ai.mit.edu> (raw)
In-Reply-To: <199607181946.PAA01041@sanguine.cygnus.com>
I agree GCC should be fixed. Obviously `#pragma weak' and __attribute__
((weak)) should use the same mechanism (they don't now). `#pragma weak'
lets you specify undefined externs as weak, which doesn't work with the
__attribute__ ((weak)) syntax (I reported this before and suggested two
possible ways to fix it, but noone ever did anything about it.)
prev parent reply other threads:[~1996-07-18 13:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
1996-07-18 0:27 H.J. Lu
1996-07-18 8:53 ` Ian Lance Taylor
1996-07-18 10:42 ` Robert.Wilhelm
1996-07-18 12:46 ` Ian Lance Taylor
1996-07-18 13:25 ` Roland McGrath [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=199607182024.QAA11657@delasyd.gnu.ai.mit.edu \
--to=roland@gnu.ai.mit.edu \
--cc=Robert.Wilhelm@physik.tu-muenchen.de \
--cc=gas2@cygnus.com \
--cc=gcc2@cygnus.com \
--cc=hjl@innovix.com \
--cc=ian@cygnus.com \
--cc=raeburn@cygnus.com \
--cc=rwilhelm@physik.tu-muenchen.de \
/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).