search for: fileheaders

?The idea itself is indeed good. Regarding to escaping: I think we should have it. Imagine the following example (I've took it from D73828). --- !ELF FileHeader: Class: ELFCLASS[[BITS]] Data: ELFDATA2LSB Type: ET_EXEC Machine: EM_386 # RUN: yaml2obj %s --docnum=4 -D BITS=32 -o %t-32bit.o # RUN: yaml2obj %s --docnum=4 -D BITS=64 -o %t-64bit.o Without escaping it would

I am adding -D k=v to yaml2obj, similar to clang -D. This makes it easy to generate {32-bit,64-bit} x {big-endian,little-endian} tests. --- !ELF FileHeader: Class: ELFCLASS[[BITS]] Data: ELFDATA2[[ENCODE]] Type: ET_DYN Machine: EM_X86_64 # RUN: yaml2obj -D BITS=32 -D ENCODE=LSB %s -o %t.32le # RUN: yaml2obj -D BITS=32 -D ENCODE=MSB %s -o %t.32le # RUN: yaml2obj

On 12/01/2013 02:14 PM, Celelibi wrote: > There is no need to have a relocation section that nothing points at. > The image is still seen as relocatable as long as the Characteristics of > the FileHeader do not say otherwise. > > Moreover, the field base_relocation_table wasn't initialized properly > leading to unpredictable bugs. > > Signed-off-by: Celelibi

----- Original Message ----- > From: "Rui Ueyama" <ruiu at google.com> > To: "Hal Finkel" <hfinkel at anl.gov> > Cc: "LLVM Developers" <llvm-dev at lists.llvm.org>, "Rafael Espindola" <rafael.espindola at gmail.com> > Sent: Thursday, October 1, 2015 11:46:05 AM > Subject: Re: lld and thread over-subscription > >

First, thanks to everyone for putting in their time to make the first truly "free" lossless audio codec. I'm co-founder of etree.org, the largest online community of lossless audio traders (currently 12,000 active members). We have been living in the shadow of Shorten for almost three years. Shorten, as most of you have come to realize, is extremely limited in terms of

...there is currently >an MD5 signature of the >unencoded audio data (i.e. >WAV file minus the >metadata). that should be >enough to fingerprint the >file. So, there's an MD5 hash of the the WAV minus the metadata, but what about the compressed audio (FLAC) minus the metadata/fileheaders? I guess this is what I'm asking about. Since, obviously the MD5 would change on the entire FLAC file whenever ID3 tags change, for example, even though the actual audio would be identical. I suppose there is no difference between using the WAV or FLAC audio data. Good deal on the other point...

----- Original Message ----- > From: "Rui Ueyama" <ruiu at google.com> > To: "Hal Finkel" <hfinkel at anl.gov> > Cc: "LLVM Developers" <llvm-dev at lists.llvm.org>, "Rafael Espindola" <rafael.espindola at gmail.com> > Sent: Thursday, October 1, 2015 12:55:20 PM > Subject: Re: lld and thread over-subscription > >

On Thu, Oct 1, 2015 at 10:55 AM, Rui Ueyama via llvm-dev < llvm-dev at lists.llvm.org> wrote: > I honestly think that the ulimit of 1024 max threads is too strict for 48 > core machine. Processes are independent each other, so it is not strange > for them to spawn as many threads as the number of cores. What's the reason > you cannot increase the limit? > Yeah, this is

Hi Rui, et al., I was experimenting yesterday with building lld on my POWER7 PPC64/Linux machine, and ran into an unfortunate problem. When running the regressions tests under lit, almost all of the tests fail like this: terminate called after throwing an instance of 'std::system_error' what(): Resource temporarily unavailable ... 5 libc.so.6 0x00000080b7847238 abort +

Hi This is a question prompted by the mac version of R, but as I see it, it should have broader interest. These days the CRAN Mac binary per default compiles every package for two architectures. First i386 and then ppc. In between the two compilation runs, any object files in pkgname/src is removed. This cleanup is necessary since otherwise Make would not recompile the object files

There is no need to have a relocation section that nothing points at. The image is still seen as relocatable as long as the Characteristics of the FileHeader do not say otherwise. Moreover, the field base_relocation_table wasn't initialized properly leading to unpredictable bugs. Signed-off-by: Celelibi <celelibi at gmail.com> --- efi/wrapper.c | 28 +++------------------------- 1

Here are the fix as suggested. For patch 2/4 I chosed to hardcore the value 512 instead of computing the fittest needed value. There are 3 reasons for that. - The header size may not need to be bigger than this in a near future. - There is an test in case increasing the header size would be needed. - It would make the code quite more complex to keep a consistent value for all the fields when the

There is no need to have a relocation section that nothing points at. The image is still seen as relocatable as long as the Characteristics of the FileHeader do not say otherwise. Moreover, the field base_relocation_table wasn't initialized properly leading to unpredictable bugs. Signed-off-by: Celelibi <celelibi at gmail.com> --- I'm not 100% positive about the uselessness of the

The goal of this proposal is to introduce a new type of YAML section for yaml2obj that allows the population of ELF .dynamic entries via a list of tag and value pairs. These entries are interpreted (and potentially validated) before being written to the .dynamic section. The simplest way to satisfy this requirement is for all dynamic entry values to be numeric values. Unfortunately, this

The PE headers of the generated efi file were quite buggy. And since OVMF perform a few consistency checks, syslinux was unable to run on it. I don't pretend to have a thorough understanding of the PE+ headers, some bugs may remain. :) Celelibi (4): efi: Fix PE header field rva_and_sizes_nr efi: Location, size and alignment of .text section efi: Useless relocations in PE file efi: PE

The Wine development release 1.1.35 is now available. What's new in this release (see below for details): - Support for OLE transacted storage. - Better certificate checking on secure connections. - More progress on the 16-bit separation. - Left 4 Dead 2 DRM really supported now. - MSI performance improvements. - 64-bit fixes in debugger support. - Various bug fixes. The source

The Wine development release 1.1.44 is now available. What's new in this release (see below for details): - Many more new icons. - Support for 32-bit prefixes with a 64-bit Wine. - Many additional msvcr80/90 functions. - Improvements to Bidi handling. - More complete mmdevapi (Win7 audio) support. - Improved handling of MSI patches. - A number of fixes for desktop menus. -

Here is the bulk of the sanitizing. My residual doubts center around the question whether we still do/want to support (un)compressed *byte*code in 2.0/2.1. I need a definitive word on this to proceed. My understanding is that bytecode is already gone, but there are still some functions/enums that really deal with *byte*code (instead of *bit*code). I did not touch those areas, so the attached