public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "khimov at altell dot ru" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/48200] linking shared library with LTO results in different exported symbols
Date: Mon, 16 Jun 2014 14:28:00 -0000 [thread overview]
Message-ID: <bug-48200-4-DLx7bq1ldK@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-48200-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=48200
Roman Khimov <khimov at altell dot ru> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |khimov at altell dot ru
--- Comment #10 from Roman Khimov <khimov at altell dot ru> ---
I can confirm the same bug with pciutils 3.2.1 and GCC 4.9.0, although now it's
pci_fill_info_v32().
next prev parent reply other threads:[~2014-06-16 14:28 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-19 2:21 [Bug lto/48200] New: " zeev.tarantov at gmail dot com
2011-03-21 13:12 ` [Bug lto/48200] " rguenth at gcc dot gnu.org
2011-03-21 18:27 ` zeev.tarantov at gmail dot com
2011-03-21 19:24 ` zeev.tarantov at gmail dot com
2011-03-22 0:14 ` zeev.tarantov at gmail dot com
2011-03-22 10:17 ` rguenth at gcc dot gnu.org
2011-03-22 10:19 ` rguenth at gcc dot gnu.org
2011-03-23 0:21 ` hubicka at ucw dot cz
2011-03-23 10:17 ` rguenth at gcc dot gnu.org
2011-03-23 13:25 ` hubicka at ucw dot cz
2014-06-16 14:28 ` khimov at altell dot ru [this message]
2014-08-05 7:19 ` amodra at gmail dot com
2020-04-15 12:46 ` [Bug lto/48200] Implement function attribute for symbol versioning (.symver) mark at gcc dot gnu.org
2020-05-06 13:45 ` hubicka at gcc dot gnu.org
2021-01-04 9:41 ` mark at gcc dot gnu.org
2021-08-30 4:35 ` pinskia at gcc dot gnu.org
2021-08-30 4:37 ` pinskia at gcc dot gnu.org
2022-01-09 0:37 ` pinskia at gcc dot gnu.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=bug-48200-4-DLx7bq1ldK@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).