public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <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: Tue, 22 Mar 2011 10:19:00 -0000	[thread overview]
Message-ID: <bug-48200-4-hVUw8Ziue0@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-48200-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48200

--- Comment #6 from Richard Guenther <rguenth at gcc dot gnu.org> 2011-03-22 10:13:49 UTC ---
Btw, the minimal partition size is quite small (1000), 10 times smaller
than our large-unit-insns inline limit and 2.7 times smaller than our
large function inline limit.  Upping that limit by a factor of 10 magically
solves this problem by only using a single partition automagically
(it looks to me that it should be similar to large-unit-insns anyway).


  parent reply	other threads:[~2011-03-22 10:14 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 [this message]
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
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-hVUw8Ziue0@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).