public inbox for gas2@sourceware.org
 help / color / mirror / Atom feed
From: Ian Lance Taylor <ian@cygnus.com>
To: Robert.Wilhelm@Physik.TU-Muenchen.DE
Cc: 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 12:46:00 -0000	[thread overview]
Message-ID: <199607181946.PAA01041@sanguine.cygnus.com> (raw)
In-Reply-To: <9607181742.AA01549@nugget.cip.physik.tu-muenchen.de>

   From: Robert.Wilhelm@Physik.TU-Muenchen.DE
   Date: Thu, 18 Jul 1996 19:42:13 +0200 (MET DST)

   > The assembler has issued this warning for over a year, including the
   > 2.6 release.  I recently (July 5) changed the warning into an error.
   > Do you receive a warning when you use an earlier version of the
   > binutils?

   gas 2.5.2linux   no message
   gas 2.6.0.2      warning
   gas 2.7          error

   BTW: The current gcc snapshot (ss-960707) produces the same asm-output as
   gcc 2.7.2.

This program works correctly when compiled by gcc.  It does not try to
define foo as both weak and global.

extern int foo () __attribute__ ((weak));
foo ()
{
}

I'm inclined to think that if gcc wants to handle #pragma weak, it
should do it the same way as __attribute__ ((weak)).  I think the
current assembler behaviour is reasonable, although I can change it if
necessary.

Ian


  reply	other threads:[~1996-07-18 12:46 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 [this message]
1996-07-18 13:25       ` Roland McGrath

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=199607181946.PAA01041@sanguine.cygnus.com \
    --to=ian@cygnus.com \
    --cc=Robert.Wilhelm@Physik.TU-Muenchen.DE \
    --cc=gas2@cygnus.com \
    --cc=gcc2@cygnus.com \
    --cc=hjl@innovix.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).