From: Robert.Wilhelm@Physik.TU-Muenchen.DE
To: ian@cygnus.com (Ian Lance Taylor)
Cc: hjl@innovix.com, gcc2@cygnus.com, raeburn@cygnus.com,
gas2@cygnus.com, rwilhelm@Physik.TU-Muenchen.DE (Robert Wilhelm)
Subject: Re: Bugs in gcc or binutils 2.7?
Date: Thu, 18 Jul 1996 10:42:00 -0000 [thread overview]
Message-ID: <9607181742.AA01549@nugget.cip.physik.tu-muenchen.de> (raw)
In-Reply-To: <199607181553.LAA25878@sanguine.cygnus.com>
> 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.
$ cat tt.c
#pragma weak foo
foo()
{}
$ gcc -S tt.c
$ cat tt.s
.file "tt.c"
.version "01.01"
gcc2_compiled.:
.text
.align 16
.globl foo
.type foo,@function
foo:
pushl %ebp
movl %esp,%ebp
.L1:
movl %ebp,%esp
popl %ebp
ret
.Lfe1:
.size foo,.Lfe1-foo
.weak foo
.ident "GCC: (GNU) 2.7.2"
$ as -v tt.s
GNU assembler version cygnus/linux-2.5.2l.15 (i486-linux), using BFD version cygnus/linux-2.5.2l.11
$ as2 -v tt.s
GNU assembler version 2.6 (i586-unknown-linux), using BFD version 2.6.0.2
tt.s: Assembler messages:
tt.s:17: Warning: foo already declared as global
$ as.new -v tt.s
GNU assembler version 2.7 (i486-unknown-linux), using BFD version 2.7
tt.s: Assembler messages:
tt.s:17: Error: foo already declared as global
--
Robert Wilhelm rwilhelm@physik.tu-muenchen.de robert@gaston.camelot.de
next prev parent reply other threads:[~1996-07-18 10:42 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 [this message]
1996-07-18 12:46 ` Ian Lance Taylor
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=9607181742.AA01549@nugget.cip.physik.tu-muenchen.de \
--to=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).