similar to: [LLVMdev] Implementing minimal debug info (-g1?) for Clang

On Apr 5, 2012, at 10:24 AM, Alexey Samsonov <samsonov at google.com> wrote: > Hi! > > Currently Clang "-g" flag emits full debug info, which is fine for debugging, but increases the binary size significantly. > It may be useful to produce less debug info, that is still enough for collecting nice stack traces with file names and line numbers, > but would introduce

Hello, Groups in asterisk are summarized here ( http://www.voip-info.org/wiki/view/Channels+and+Groups). Is there any difference between DAHDI/G1/0123456789 and DAHDI/g1/0123456789 (as I've been advised in another thread, to switch from one notation to the other and I can't see the reason behind that) ? Regards -------------- next part -------------- An HTML attachment was scrubbed...

I am using some functions from package clusterSim to evaluate the best clusters layout. Here is the features vector I am using to cluater 12 signals: > alpha.vec [1] 0.8540039 0.8558350 0.8006592 0.8066406 0.8322754 0.8991699 0.8212891 [8] 0.8815918 0.9050293 0.9174194 0.8613281 0.8425293 In the following I pasted an excerpt of my program:

Dear R Users: I am new to R and I am trying to do a cluster analysis on a single continuous variable using the Agnes [Agglomerative Nesting (Hierarchical Clustering) ] in the Package ‘cluster’. I was able to apply this clustering method to my data: ward1 <- Agnes(balances, diss= FALSE, metric = "euclidean", stand = TRUE, method = "ward", keep.diss =TRUE, keep.data =

greetings, for those of you in the know, may i have some assistance in helping to make better decisions in purchasing more used server toys to install CentOS on please? :-) in the Compaq Proliant Rackmount DL380 line, the one that looks like the older 1850R is called a G1 meaning Generation 1 right? and then the DL380 G2 is a redesign that is gray and just has 6 drive bays up front correct?

Hello everybody, I have a strange comportment with oh323 and asterisk, I'start testing asterisk but with this I can't understant plesae help me ! Thanks Eltorio ---------------------------------------------------------- 1/PB: I can't dial from a H323 extensions (registered on a GNU GK) to a Modem[i4l] line ---------------------------------------------------------- Nothing happens

greetings i have a few dual P3 Compaq 1850R units and use compaq smartstart 5.5 on them before a CentOS 4 load i have acquired some dual P3 Compaq DL380 G1 i.e. Generation 1 units and am wondering which specific smartstart download i should be using for them from this URL below h18004.www1.hp.com/support/files/server/us/subscription/ssdownloads.asp would someone please share their experience

On Thu, Aug 28, 2014 at 11:51 AM, Alexey Samsonov <vonosmas at gmail.com> wrote: > This sounds great. Teaching backend about the -gmlt might help us in > another way: we might enforce full debug info generation in the frontend > for -fsanitize= flags, then rely on some parts of this debug info in > instrumentation passes and prune it before the actual object file >

On Sun, Oct 26, 2014 at 7:23 PM, Xinliang David Li <xinliangli at gmail.com> wrote: > The fundamental questions we need to answer are the following: > FWIW, there was a longer discussion on the lists when the actual option was added. I'll try to relay my memory of that discussion, but you might need to track it down or involve some of the other people who participated in it.

I'm not sure if this was intended, but it's going to be a problem for sample profiles. When we compile with -gmlt, the profiler expects to find the line number for all the function headers so that it can compute relative line locations for the profile. The tool that reads the ELF binary is not finding them, so it writes out absolute line numbers, which are impossible to match during the

In an effort to fix inlined information for backtraces under DWARF Fission in the absence of the split DWARF (.dwo) files, I'm planning on adding -gmlt-like data to the .o file, alongside the skeleton CU. Since that will involve teaching the LLVM about -gmlt (moreso than it already has - the debug info LLVM metadata already describes -gmlt for the purposes of omitting pubnames in that case) I

On Fri, Oct 24, 2014 at 4:06 PM, Xinliang David Li <xinliangli at gmail.com> wrote: > Diego, > > I think sampleFDO needs to be designed in a way which can protect itself > from future breakage like this. The roots in the unnecessary dependency of > sample FDO on gmlt setting. It is totally reasonable to tune debug binary > size by changes like this. > > The right way

On Fri Oct 24 2014 at 6:11:21 PM David Blaikie <dblaikie at gmail.com> wrote: > On Fri, Oct 24, 2014 at 2:48 PM, Diego Novillo <dnovillo at google.com> > wrote: > >> I'm not sure if this was intended, but it's going to be a problem for >> sample profiles. >> >> When we compile with -gmlt, the profiler expects to find the line number >>

On Fri Oct 24 2014 at 6:21:14 PM David Blaikie <dblaikie at gmail.com> wrote: > On Fri, Oct 24, 2014 at 3:16 PM, Diego Novillo <dnovillo at google.com> > wrote: > >> >> >> On Fri Oct 24 2014 at 6:11:21 PM David Blaikie <dblaikie at gmail.com> >> wrote: >> >>> On Fri, Oct 24, 2014 at 2:48 PM, Diego Novillo <dnovillo at

On 10/30/13 7:09 PM, Philip Reames wrote: > David, Quentin - Thanks for the feedback. Responses inline. > > On 10/30/13 11:21 AM, David Blaikie wrote: >> Actually CCing Eric. >> >> >> On Wed, Oct 30, 2013 at 11:00 AM, Quentin Colombet >> <qcolombet at apple.com <mailto:qcolombet at apple.com>> wrote: >> >> Philip, >>

On Sun, Oct 26, 2014 at 4:59 PM, Eric Christopher <echristo at gmail.com> wrote: > On Fri, Oct 24, 2014 at 3:27 PM, Diego Novillo <dnovillo at google.com> > wrote: > > > > > > On Fri Oct 24 2014 at 6:21:14 PM David Blaikie <dblaikie at gmail.com> > wrote: > >> > >> On Fri, Oct 24, 2014 at 3:16 PM, Diego Novillo <dnovillo at

On Oct 30, 2013 7:25 PM, "Philip Reames" <listmail at philipreames.com> wrote: > > On 10/30/13 7:09 PM, Philip Reames wrote: >> >> David, Quentin - Thanks for the feedback. Responses inline. >> >> On 10/30/13 11:21 AM, David Blaikie wrote: >>> >>> Actually CCing Eric. >>> >>> >>> On Wed, Oct 30, 2013 at

On Sun, Oct 26, 2014 at 3:47 PM, Jeremy Lakeman <Jeremy.Lakeman at gmail.com> wrote: > This sounds like a problem best solved by tracking source code movement via > your source control system. > If you know the commit of the code that produced the sample, you should be > able to use source control history / diffs to translate absolute line > numbers to the location where the

On Wed, Aug 27, 2014 at 4:53 PM, Chandler Carruth <chandlerc at google.com> wrote: > > On Wed, Aug 27, 2014 at 4:40 PM, David Blaikie <dblaikie at gmail.com> wrote: > >> DW_AT_frame_base (the location of the frame pointer - is that needed for >> symbolication?) > > > I think this is used by libunwind style stack unwinders in conjunction > with

On Wed, Oct 30, 2013 at 8:58 PM, Eric Christopher <echristo at gmail.com>wrote: > > On Oct 30, 2013 7:25 PM, "Philip Reames" <listmail at philipreames.com> > wrote: > > > > On 10/30/13 7:09 PM, Philip Reames wrote: > >> > >> David, Quentin - Thanks for the feedback. Responses inline. > >> > >> On 10/30/13 11:21 AM,