public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/58990] G++ generates duplicate labels for linux 32-bit when optimization+LFS is enabled
Date: Sun, 10 Nov 2013 21:07:00 -0000 [thread overview]
Message-ID: <bug-58990-4-x98aYrYcXA@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-58990-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58990
Andrew Pinski <pinskia at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|WAITING |RESOLVED
Resolution|--- |INVALID
--- Comment #7 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
The issue is simple, GCC is generating the correct assembly. The problem is
C++ defines extern inline differently from GNU C90 and more like C99's extern
inline. We had a way to fix up the header files for this specific issue but it
looks like it is not happening for your version of glibc or rather the fixed up
headers are not being used as the package installer did not do that which means
this is a bug in your distro's binary package and should be reported to them.
prev parent reply other threads:[~2013-11-10 21:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-04 21:13 [Bug c++/58990] New: " novulae at hotmail dot com
2013-11-04 21:57 ` [Bug c++/58990] " hjl.tools at gmail dot com
2013-11-04 22:06 ` pinskia at gcc dot gnu.org
2013-11-05 16:12 ` novulae at hotmail dot com
2013-11-05 16:13 ` novulae at hotmail dot com
2013-11-05 16:13 ` novulae at hotmail dot com
2013-11-05 16:14 ` novulae at hotmail dot com
2013-11-10 21:07 ` pinskia at gcc dot gnu.org [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=bug-58990-4-x98aYrYcXA@http.gcc.gnu.org/bugzilla/ \
--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).