search for: stack_sizes

This series consists of improvements to Xen''s ability to print traces of its own stack, and specifically for the stack overflow case to be able to use frame pointers in a debug build. I have dev tested the series in debug and non-debug cases, with and without memory guards, and I believe that all the stack traces look correct. However, I would greatly appreciate a second opinion on the

>>> With GNU gold (GNU Binutils 2.29.51.20171006) 1.14 have an assert: >>> ~/LLVM/Release/bin/clang++ test.cpp -ffunction-sections -o test.o >>> /usr/local/bin/ld: internal error in layout_eh_frame_section, at >>> .././../gold/object.cc:1309 >>> It is that place: >>> https://github.com/gittup/binutils/blob/gittup/gold/object.cc#L1372

This series consists of improvements to Xen''s ability to print traces of its own stack, and specifically for the stack overflow case to be able to use frame pointers in a debug build. I have dev tested the series in debug and non-debug cases, with and without memory guards, and I believe that all the stack traces look correct (given the available information Xen has), and that the

>> With GNU gold (GNU Binutils 2.29.51.20171006) 1.14 have an assert: >> ~/LLVM/Release/bin/clang++ test.cpp -ffunction-sections -o test.o >> /usr/local/bin/ld: internal error in layout_eh_frame_section, at >> .././../gold/object.cc:1309 >> It is that place: >> https://github.com/gittup/binutils/blob/gittup/gold/object.cc#L1372 >> Did not investigate it,

...ou do any profiling of the code? Were the slowdowns you were seeing fundamental (i.e. due to IO) or could a more optimal implementation reduce the slowdown? Did you do any end to end timings for compilation + link time? The same issues arise for all metadata sections: .eh_frame .debug_* .stack_sizes etc... In our proprietary linker we've had to implement special handling for each of these sections, which we'd love to be able to remove or reduce. One fundamental problem is overhead. I posted about this on the gabi list: https://groups.google.com/d/msg/generic-abi/A-1rbP8hFC...

Hi llvmdev! I've been working on adding coroutines to LLVM. Mentioned below is the implementation plan I'm following, for suggestions, flames and other input. Using segmented stacks is a prerequisite. The idea is to associate every coroutine with a coroutine descriptor. A coroutine descriptor consists of four words: w0, w1, w2 and w3. w0 always contains the _launcher_, and invoking a

...quires the linker and other tools to > have to do unnecessary string comparisons, which are slower and messier > than switching on the sh_type field. > Yes, having a specific ELF section type would be great. Though I am clueless about how this change will be received given that the ".stack_sizes" section also uses SHT_PROGBITS. I can definitely look into it if I get some assurance. James > > On Wed, 16 Sep 2020 at 22:00, Rahman Lavaee <rahmanl at google.com> wrote: > >> Hi All, >> >> Following up on >> https://lists.llvm.org/pipermail/llvm-dev/2...

This patch series implements SMP boot for arch/arm, as far as getting all CPUs up and running the idle loop. Changes from v1: - moved barriers out of loop in udelay() - dropped broken GIC change in favour of explanatory comment - made the increment of ready_cpus atomic (I couldn''t move the increment to before signalling the next CPU because the PT switch has to happen between

Hello all! I recently install R-1.2.3 and Omegahat SJava pkg (formely Java pkg) 0.62 and tried running the examples by issuing "scripts/RJava --example --gui=none" and I got the following: Error in dyn.load(x, as.logical(local), as.logical(now)) : unable to load shared library "/usr/lib/R/library/ctest/libs/ctest.so": ld.so.1:

On 07/28/2011 05:31 PM, Sanjoy Das wrote: > Hi llvmdev! > > I've been working on adding coroutines to LLVM. Mentioned below is the > implementation plan I'm following, for suggestions, flames and other > input. Using segmented stacks is a prerequisite. I think my only comment is that, while this would probably work, implementing it in C with a bit of assembly for

While it is great that LLVM has an IR Verifier, its a little troublesome to use because it separates the point of detection from the source of the problem. That is, the verifier gets run on a module or function after its been built. By that point, the compiler's state has moved past the point at which the error was placed into the module or function. Trying to track down the source of the

Hi, This is the fifth version of this patch series. With the Versatile Express TC2, it''s possible to boot only with A7 or A15. If the user choose to boot with only A7, the CPU ID will start at 0x100. As Xen relies on it to set the logical ID and the GIC, it won''t be possible to use Xen with this use case. This patch series is divided in 3 parts: - Patch 1: prepare Xen

Hi all, Centos 5.5 comes with Python 2.4.3. I wish to increase the env size for my Python shells and found this although it pertains to Python 2.5; thread.stack_size([size]) Any one have some pearls for me wether this works in <2.5 or the best way to give my Python shells more memory? I'm scheduled to tackle this tonight and would like to prep myself. Thanks in advance, - aurf

I have a IBM System x3600 series server with UEFI. I managed to compile the xen EFI (xen-4.2-unstable.efi). The machine is currently running Ubuntu with grub2. I can see a grubx64.efi in /boot/efi/EFI/ubuntu/grubx64.efi Where should I put the xen efi ? I tried creating a efi/EFI/xen/xen-4.2-unstable.efi and added it as a boot option using efibootmgr. All I get in that case is a blank screen. I

I get a link error when trying to call malloc from libcom32. I tried to simplify the case by adding the malloc to the sample hello.c in the modules directory, but I still get the following error: ld -m elf_i386 -T ../lib/com32.ld -o hello.elf hello.o ../libutil/libutil_com.a ../lib/libcom32.a /usr/lib64/gcc-lib/x86_64-suse-linux/3.3.3/32/libgcc.a ../lib/libcom32.a(malloc.o)(.text+0x13): In

minios: support COW for a zero page Permits to support sparse data. Signed-off-by: Samuel Thibault <samuel.thibault@eu.citrix.com> diff -r 27ad7ed41be2 extras/mini-os/arch/x86/mm.c --- a/extras/mini-os/arch/x86/mm.c Fri Jan 18 15:55:13 2008 +0000 +++ b/extras/mini-os/arch/x86/mm.c Fri Jan 18 16:02:32 2008 +0000 @@ -50,6 +50,7 @@ #endif unsigned long *phys_to_machine_mapping; +unsigned

libswfdec/swfdec_as_interpret.c | 65 ++------- libswfdec/swfdec_sound.c | 24 --- libswfdec/swfdec_sound.h | 4 test/trace/Makefile.am | 27 +++ test/trace/enumerate-5.swf |binary test/trace/enumerate-5.swf.trace | 6 test/trace/enumerate-6.swf |binary test/trace/enumerate-6.swf.trace | 6

libswfdec/swfdec_image.c | 113 ++++++++---- libswfdec/swfdec_image.h | 5 libswfdec/swfdec_js.c | 5 libswfdec/swfdec_js_color.c | 8 libswfdec/swfdec_js_sound.c | 7 libswfdec/swfdec_pattern.c | 3 libswfdec/swfdec_script.c | 376 +++++++++++++++++++++++++++++++++++++++--- libswfdec/swfdec_scriptable.c | 2 8 files changed, 441

libswfdec/js/jsinterp.c | 3 libswfdec/js/jsinterp.h | 1 libswfdec/swfdec_js.c | 51 +++++++++ libswfdec/swfdec_js.h | 8 + libswfdec/swfdec_js_global.c | 30 +++++ libswfdec/swfdec_js_movie.c | 181 +++++++++++++++++++++++++---------- libswfdec/swfdec_movie.c | 22 ---- libswfdec/swfdec_player.c |

The following patches made over Linus's tree fix the 2 bugs: 1. vhost worker task shows up as a process forked from the parent that did VHOST_SET_OWNER ioctl instead of a process under root/kthreadd. This was causing breaking scripts. 2. vhost_tasks didn't disable or add support for freeze requests. The following patches fix these issues by making the vhost_task task a thread under the