public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "carlo at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/17042] New: [regression 3.5] Duplicated symbol in assembly output
Date: Sun, 15 Aug 2004 23:30:00 -0000 [thread overview]
Message-ID: <20040815232958.17042.carlo@gcc.gnu.org> (raw)
I cannot manage to write a small test case that still shows this bug.
However - it must be a bug because this code compiles with all other
compiler versions and did compile fine with CVS of May 2004.
To reproduce compile the attached libcw_app.ii:
[...]
/usr/src/GNU/install/bin/../libexec/gcc/i686-redhat-linux/3.5.0/cc1plus
-fpreprocessed libcw_app.ii -quiet -dumpbase libcw_app.cc -mtune=pentiumpro
-auxbase-strip .libs/libcw_app.o -g -Wall -Woverloaded-virtual -Wundef
-Wpointer-arith -Wwrite-strings -Werror -Winline -version -fPIC -o libcw_app.s
GNU C++ version 3.5.0 20040813 (experimental) (i686-redhat-linux)
compiled by GNU C version 3.5.0 20040813 (experimental).
GGC heuristics: --param ggc-min-expand=90 --param ggc-min-heapsize=113141
as -V -Qy -o .libs/libcw_app.o libcw_app.s
GNU assembler version 2.14.90.0.8 (i386-redhat-linux) using BFD version
2.14.90.0.8 20040114
libcw_app.s: Assembler messages:
libcw_app.s:191: Error: symbol `__dso_handle' is already defined
The problem is that `__dso_handle' is emitted twice in libcw_app.s,
while it should only be emitted once.
--
Summary: [regression 3.5] Duplicated symbol in assembly output
Product: gcc
Version: 3.5.0
Status: UNCONFIRMED
Keywords: wrong-code
Severity: normal
Priority: P2
Component: middle-end
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: carlo at gcc dot gnu dot org
CC: gcc-bugs at gcc dot gnu dot org
GCC host triplet: i686-redhat-gnu-linux
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=17042
next reply other threads:[~2004-08-15 23:30 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-15 23:30 carlo at gcc dot gnu dot org [this message]
2004-08-15 23:33 ` [Bug middle-end/17042] " carlo at gcc dot gnu dot org
2004-08-15 23:36 ` [Bug c++/17042] [3.5 regression] " pinskia at gcc dot gnu dot org
2004-08-15 23:44 ` pinskia at gcc dot gnu dot org
2004-08-16 17:34 ` pinskia at gcc dot gnu dot org
2004-08-17 6:25 ` mmitchel at gcc dot gnu dot org
2004-08-17 7:20 ` pinskia at gcc dot gnu dot org
2004-10-15 5:22 ` [Bug c++/17042] [4.0 " mmitchel at gcc dot gnu dot org
2004-10-15 21:12 ` cvs-commit at gcc dot gnu dot org
2004-10-15 21:15 ` mmitchel at gcc dot gnu dot org
2004-10-15 21:18 ` cvs-commit at gcc dot gnu dot org
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=20040815232958.17042.carlo@gcc.gnu.org \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@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).