public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "darkshikari at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/43827] Intrinsic possibility: does not alias global data
Date: Wed, 21 Apr 2010 22:25:00 -0000 [thread overview]
Message-ID: <20100421222430.6845.qmail@sourceware.org> (raw)
In-Reply-To: <bug-43827-19067@http.gcc.gnu.org/bugzilla/>
------- Comment #5 from darkshikari at gmail dot com 2010-04-21 22:24 -------
One somewhat unrelated issue I had when attempting to compile using LTO: we
have about 5 arrays in C that are referenced from YASM-syntax assembly code.
Even I add __attribute__((used)), LTO/wholeprogram seems to optimize these out
in the link-time optimization step. This results in the link failing when it
comes time to link the .o files for the assembly functions.
It seems conceptually wrong that it should be impossible to reference C arrays
from asm code when using LTO + wholeprogram. Is there any way around this
beyond copy-pasting all this data, is this a bug, or is this intended behavior?
--
darkshikari at gmail dot com changed:
What |Removed |Added
----------------------------------------------------------------------------
Component|tree-optimization |c
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43827
next prev parent reply other threads:[~2010-04-21 22:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-21 3:40 [Bug c/43827] New: " darkshikari at gmail dot com
2010-04-21 9:30 ` [Bug c/43827] " rguenth at gcc dot gnu dot org
2010-04-21 22:07 ` darkshikari at gmail dot com
2010-04-21 22:09 ` pinskia at gcc dot gnu dot org
2010-04-21 22:14 ` [Bug tree-optimization/43827] " rguenth at gcc dot gnu dot org
2010-04-21 22:25 ` darkshikari at gmail dot com [this message]
2010-04-22 6:31 ` [Bug c/43827] " darkshikari at gmail dot com
[not found] <bug-43827-4@http.gcc.gnu.org/bugzilla/>
2015-03-17 6:54 ` mpolacek 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=20100421222430.6845.qmail@sourceware.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).