Displaying 20 results from an estimated 200000 matches similar to: "--keep-symbol alternative"
2009 Feb 03
0
[LLVMdev] Proposal: Debug information improvement - keep the line number with optimizations
Hi Patel,
Thanks for your comments, some reply below... (This is the first part,
I'll send the second part later)
> 2.1 Verification Flow
> > The most important of this project is to make the debug information
> > do not block any optimization by LLVM transform passes. Here I
> > propose a way to determine whether codegen is being impacted by
> > debug info.
2010 Apr 08
1
Placing the ≥ symbol in the Trellis custom strip
Hello,
I am trying to use ≥ symbol in the Trellis custom strip. The ascii ALT Key
for this symbol is 242. However, when I try "\242 90 kg" I get the ¢ symbol
in the trellis custom strip. Can some one kindly help me?
Thanking you in advance,
MNS
[[alternative HTML version deleted]]
2008 May 12
1
inserting mathematical symbols in lattice strip
I have tried without success to find a way including the square root symbol
in lattice strips as part of my conditioning labels. I have tried
supplementing by creating a list of vectors using the var.name function
coupled with the expression function used in xlab/ylab.
xyplot(adjusted_Rand_index~cluster|distance_measure, main="Level of
agreement between partitions: Wards Method",
2018 Feb 26
3
Level of support for ARM LLD
Thanks Rafael, wondering as of what is the level of support for ARM and is
it close to production quality?
Thanks
On Mon, Feb 26, 2018 at 2:06 PM, Rafael Avila de Espindola <
rafael.espindola at gmail.com> wrote:
> Not sure there is an official POC, you are probably better off asking
> whatever question you have directly on the list.
>
> Cheers,
> Rafael
>
> Sumonto
2018 Feb 27
0
Level of support for ARM LLD
I think ARM ELF is pretty good. I was able to link clang with it some
time ago and it now has support for thunks.
Cheers,
Rafael
Sumonto Ghosh <sumonto.ghosh at gmail.com> writes:
> Thanks Rafael, wondering as of what is the level of support for ARM and is
> it close to production quality?
>
> Thanks
>
> On Mon, Feb 26, 2018 at 2:06 PM, Rafael Avila de Espindola <
2018 Feb 27
2
Level of support for ARM LLD
Is there a regression bot with a list of tests or alike
Thanks
On Mon, Feb 26, 2018 at 4:19 PM Rafael Avila de Espindola <
rafael.espindola at gmail.com> wrote:
> I think ARM ELF is pretty good. I was able to link clang with it some
> time ago and it now has support for thunks.
>
> Cheers,
> Rafael
>
>
> Sumonto Ghosh <sumonto.ghosh at gmail.com> writes:
>
2013 Jun 17
1
Odd behavior of symbol objects with classes/attributes
I've been trying to add classes and attributes to symbol objects
(created with quote()), and the behavior is very strange, as
illustrated in the examples below.
If symbols aren't meant to have classes and attributes attached to
them, then perhaps R should throw errors when you attempt to do it?
# Using str() strips class from object
x <- quote(foo)
class(x) <- "bar"
2018 Feb 27
0
Level of support for ARM LLD
Hello Sumonto,
There are several upstream build bots that run the Arm specific LLD
tests. You can find these tests in the lld/test/ELF directory, they
all start with arm. At Linaro we are planning to set up a build-bot,
modelled on the equivalent AArch64 one that does a 2 stage build of
clang with LLD as the linker, this will also include running the test
suite.
For the ELF port; the major Arm
2009 Nov 13
1
Trellis settings get lost when printing to pdf
Hi all,
I've got some problems when changing the trellis settings for the lattice plots. The plots look exactly as I want them to when calling show.settings() as well as when plotting them in the graphical window. But when printing to a pdf file, none of the settings are used!? Does anyone know what might have happened? Because the when changing the trellis settings, these should remain in
2012 Nov 12
0
[LLVMdev] lld deadstrip atoms
On Nov 9, 2012, at 10:31 AM, Shankar Easwaran wrote:
> Hi Nick,
>
> Dead stripping optimization needs a way to setup the roots which are live. The current code in Resolver does it by
>
> 1) setting all the global defined atoms to be the live set when building shared libraries (_options.allGlobalsAreDeadStripRoots)
> 2) Or, uses a list of names that are dead strip roots (other
2017 Apr 23
0
impossible to link against libtheoraenc (missing symbol th_comment_query_count)
I've got a huge problem with libtheora. All is fine if I link only
against libtheoradec but as soon as I try to link also against
libtheoraenc everything breaks down:
libtheoraenc.so.1 dlerror: libtheoraenc.so.1: undefined symbol:
th_comment_query_count.
I've checked with NM to see how the libraries depend on each other:
nm libtheoraenc.so.1 | grep th_comment_query_count
2009 Feb 03
0
[LLVMdev] Proposal: Debug information improvement - keep the line number with optimizations
Hi Patel,
Here is second part of my reply.
> 2. Proposed Work Plan
> > This section defines a proposed work plan to accomplish the
> > requirements that we desires. The work plan is broken into several
> > distinct phases that follow a logical progression of modifications
> > to the LLVM software.
> >
> > 2.1 Phase 1: Establish the testing
2013 Jun 09
1
Force to strip all symbols from ELFs when using rpmbuild on CentOS
Hello.
What's the proper way to remove *all symbols* from ELF binaries when
building packages with rpmbuild on CentOS? Seems that an out of the box
rpmbuild install only discards debugging symbols (strip -g).
That's the default configuration for %__os_install_post on CentOS, the
step in charge on stripping binaries:
$ rpmbuild --showrc
(..)
-14: __os_install_post
2012 Nov 09
2
[LLVMdev] lld deadstrip atoms
Hi Nick,
Dead stripping optimization needs a way to setup the roots which are
live. The current code in Resolver does it by
1) setting all the global defined atoms to be the live set when building
shared libraries (_options.allGlobalsAreDeadStripRoots)
2) Or, uses a list of names that are dead strip roots (other types)
Question:-
***********
How are the dead strip root names supposed to be
2008 May 12
1
Mathematical annotation in lattice strip: Is it possible?
I have tried without success to find a way including the square root symbol
in lattice strips as part of my conditioning labels. I have tried
supplementing by creating a list of vectors using the var.name function
coupled with the expression function used in xlab/ylab.
xyplot(adjusted_Rand_index~cluster|distance_measure, main="Level of
agreement between partitions: Wards Method",
2011 Aug 26
1
occasional dovecot crash, core captured but no symbol table info?
Dovecot is crashing occasionally for me. Today it crashed six times in quick succession, as I fired up a computer (Mac) I hadn't used in a while, and my mail application (Apple Mail) tried to synchronize many large mailboxes.
The log entries look like this:
Aug 26 10:26:15 computer dovecot: dovecot: child 23223 (imap) killed with signal 6 (core dumped)
Aug 26 10:26:30 computer dovecot:
2004 Mar 04
2
lattice, different plotting symbols
Hi,
I am trying to plot different variables from a data.frame using lattice's
xyplot using code like that below. How do I specify a symbol and color
for the variable 'prob' and different one's for 'll.prob'?
Thanks, Matt
xyplot( prob + ll.prob ~ time.eff |stat.id + time.out ,data = OUT,
allow.multiple = TRUE,
layout = c(6,3), as.table = TRUE ,
2009 Feb 02
1
[LLVMdev] Proposal: Debug information improvement - keep the line number with optimizations
Hi,
I've been thinking about how to keep the line number with the llvm
transform/Analysis passes.
Basically, I agree with Chris's notes (
http://www.nondot.org/sabre/LLVMNotes/DebugInfoImprovements.txt), and I
will follow his way to turn on the line number information when optimization
enabled.
Here is a detailed proposal:
1. Introduction
At the time of this writing, LLVM's
2010 Nov 07
1
Sweave: option keep.source=TRUE and package cacheSweave
Dear all,
When I use the cacheSweave package together with the Sweave option
keep.source = TRUE, all the LaTeX code before the Sweave code chunk is
included in the TeX file to be compiled. For example, with the
following Sweave file
\documentclass[12pt]{article}
\usepackage[nogin]{Sweave}
% Sweave options
\SweaveOpts{keep.source=TRUE, strip.white=TRUE, eps=FALSE, pdf=TRUE}
\begin{document}
2018 Jan 24
0
Should llvm-nm classify Mach-O __DATA, __common symbols as BSS?
Hello LLVM-Devs,
Perhaps a pedantic question, but I'm wondering how __DATA,__common and
__DATA,__bss symbols differ, and whether llvm-nm ought not classify
the former as type "B" as it does the latter:
$ cat bss.c
int i;
static int si __attribute__((used));
$ clang -fno-common -c bss.c
$ nm bss.o
0000000000000000 S _i
0000000000000004 b _si
$ nm -m bss.o
0000000000000000