search for: convinations

>Not quite sure what you mean by "on linker side" - but I guess you mean using linker features like comdats etc, rather than DWARF parsing/reassembly/etc. I mean that it probably not a good idea for external library. I feel it is much more convinent to do such proccessing in a linker. Linker do and knows much more about things like sections that are ICFed, eliminated, about COMDATs

>Postprocessing (ie: running a tool on the fully linked binary with the debug info we have today, and having the tool reprocess the debug info to make it more >compact) is an option, but wouldn't help address the problem you started with - that the output can't fit the large offsets, so the output is invalid/broken. So that >output would be broken before the postprocessing step

>*nod* That's been the historic ELF+DWARF approach, but both MacOS (with dsyms+DWARF) and Windows >(COFF+CodeView+PDB) don't do it that way, and instead involve the linker to a degree. >Mostly I'm wondering if it'd be reasonable to (and if anyone would be interested in doing it) do >something more like the PDB support - fully debug-aware linking. Honestly saying I only

于 2013/3/24 0:07, Joerg Sonnenberger 写道: > On Sat, Mar 23, 2013 at 04:59:49PM +0100, Tobias Grosser wrote: >> With Chris's reply you also got the general OK to upstream the >> patch, _AFTER_ the actual patches have been reviewed. > One thing I was asking on IRC for is whether it makes sense for new > backends to be committable in incremental steps. Especially for a >

On Sat, Mar 23, 2013 at 04:59:49PM +0100, Tobias Grosser wrote: > With Chris's reply you also got the general OK to upstream the > patch, _AFTER_ the actual patches have been reviewed. One thing I was asking on IRC for is whether it makes sense for new backends to be committable in incremental steps. Especially for a complete backend like this, e.g. the asm parser would make a

On Sat, Dec 16, 2017 at 11:40 AM George Rimar <grimar at accesssoftek.com> wrote: > Or following workflow: > > Split dwarf is used to make linker to proccess less, like relocations, > right ? > Partly, though the main motivation as far as I know, was to have to provide fewer bytes to the linker at all. That's why something like Apple's scheme (leave the debug info in

Hola a todos: efectivamente, esas son las librerias que convine tener instaladas. Llevaré los datos que utilizaremos en un pendrive (por si acaso falla la wifi) y también el *.md del código para poder seguir la demo sin escribir todo el código! Para esto, yo creo que lo mejor es abrir el *.md con R Studio. Esta tarde nos vemos! -- Beatriz Martínez @_bmartinez_

>> From: Rui Ueyama <ruiu at google.com> >> Date: Mon, 19 Dec 2016 20:08:59 -0600 >> >> LGTM > >Great. I don't have commit access, so it would be great if you could >commit this change for me. > >Just realized that that I should have sent this to llvm-commits >instead. Apologies for that. > >I have some further fixes. Is Phabricator

On Tue, Jan 27, 2015 at 09:24:35AM +0800, Hu Tao wrote: > On Wed, Jan 21, 2015 at 01:58:02PM +0000, Richard W.M. Jones wrote: > > On Fri, Jan 16, 2015 at 10:23:35AM +0800, Hu Tao wrote: > > [...] > > > > Thanks for these patches. I will push all of them shortly *except*: > > Thanks! > > > > > > New API: btrfs_balance_status > > >

Hi all, I have something like this : user has_many lists list has_many items I want to validate that the currently logged-in user is the owner of the list an item is being added to. I can do it in "item/create" by doing something like : class item def create @list = List.new( @params[ "list" ][ "id" ] ) if @session[ "user"

Hola Beatriz, Si me pasas el *.md lo subo a un Dropbox y si no es muy grande lo subo a R-Hispano (linkándolo a la agenda).... Saludos, Carlos. El 29 de octubre de 2013 15:56, Gregorio R. Serrano <grserrano@ccee.ucm.es>escribió: > Hola. > > ¿Nos podemos descargar el material de alguna parte antes de ir? > > Gracias > > > El 29 de octubre de 2013 14:58, Beatriz

>If you're interested in things you can do in the linker for this - you might consider something more aggressive: Fully DWARF aware deduplication. > >This could be done hopefully by reusing some of the code in the dsymutil implementation in LLVM. > >This would be much more effective (and without the possible context-sensitive tradeoffs) than using type units. >Though

...trunk... I see from telenet asterisk -r that the trunk pass the call to the cellsocket....I see that it says Zap/4-1 answered.....but to make it work I have to press the # in the cisco phone, then I see the cellphone dialing, ....I followed the instruction from the other post and have tried several convinations and still don't put the # at end, Do you have some samples?? thanks again!!!!!! -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.digium.com/pipermail/asterisk-users/attachments/20050512/722b4d85/attachment.htm

On Wed, Jan 21, 2015 at 01:58:02PM +0000, Richard W.M. Jones wrote: > On Fri, Jan 16, 2015 at 10:23:35AM +0800, Hu Tao wrote: > [...] > > Thanks for these patches. I will push all of them shortly *except*: Thanks! > > > New API: btrfs_balance_status > > New API: btrfs_scrub_status > > - These ones currently dump the status into a string. Generally

On Sat, Mar 23, 2013 at 12:34 PM, Jiong Wang <jiwang at tilera.com> wrote: > 于 2013/3/24 0:07, Joerg Sonnenberger 写道: > > On Sat, Mar 23, 2013 at 04:59:49PM +0100, Tobias Grosser wrote: >> >>> With Chris's reply you also got the general OK to upstream the >>> patch, _AFTER_ the actual patches have been reviewed. >>> >> One thing I was

I'm pleased to see another project increasing compatibility with windows clients, by the addition of NTLM login support, but I'm a bit worried about a few implementation details, and hope to offer an alternate approach. I mean no disrespect to those who have implemented to the code so far, but I feel that the idea of 'everybody re-implement NTLM' is prone to failure. Firstly, to

Hola. ¿Nos podemos descargar el material de alguna parte antes de ir? Gracias El 29 de octubre de 2013 14:58, Beatriz Martínez <mtnezb@gmail.com>escribió: > Hola a todos: > > efectivamente, esas son las librerias que convine tener instaladas. > > Llevaré los datos que utilizaremos en un pendrive (por si acaso falla la > wifi) y también el *.md del código para poder

el material lo podéis descargar de aquí http://goo.gl/PT30FB El 29 de octubre de 2013 15:59, Carlos Ortega <cof@qualityexcellence.es>escribió: > Hola Beatriz, > > Si me pasas el *.md lo subo a un Dropbox y si no es muy grande lo subo a > R-Hispano (linkándolo a la agenda).... > > Saludos, > Carlos. > > > El 29 de octubre de 2013 15:56, Gregorio R. Serrano

The Asterisk Development Team has announced the release of Asterisk 1.2.37, 1.4.27.1, 1.6.0.19, and 1.6.1.11. These releases are available for immediate download at http://downloads.asterisk.org/pub/telephony/asterisk/ These releases have been created in response to a SIP remote crash vulnerability. Additionally, Asterisk versions 1.4.27.1, 1.6.0.19, and 1.6.1.11 also contain an SDP regression

The Asterisk Development Team has announced the release of Asterisk 1.2.37, 1.4.27.1, 1.6.0.19, and 1.6.1.11. These releases are available for immediate download at http://downloads.asterisk.org/pub/telephony/asterisk/ These releases have been created in response to a SIP remote crash vulnerability. Additionally, Asterisk versions 1.4.27.1, 1.6.0.19, and 1.6.1.11 also contain an SDP regression