similar to: [LLVMdev] [RFC/PATCH][4/4] Support System Z as host architecture

Commit-ID: 1cd11aaed1dece773c6b1ce2e99a0fe98b51321e Gitweb: http://git.kernel.org/?p=libs/klibc/klibc.git;a=commit;h=1cd11aaed1dece773c6b1ce2e99a0fe98b51321e Author: Ben Hutchings <ben at decadent.org.uk> AuthorDate: Thu, 27 Aug 2020 01:58:19 +0100 Committer: Ben Hutchings <ben at decadent.org.uk> CommitDate: Thu, 27 Aug 2020 03:51:11 +0100 [klibc] alpha: Fix definitions of

Following example from usr/include/arch/i386/klibc/archsignal.h: The in-kernel headers for arm still have libc5 crap in them. Reconsider using <asm/signal.h> when/if it gets cleaned up; for now, duplicate the definitions here. Signed-off-by: Jon Ringle <jon at ringle.org> --- usr/include/arch/arm/klibc/archsignal.h | 112 ++++++++++++++++++++++++++++++- 1 files changed, 110

Hi Chris, I've CC'd Eric Botcazou in the hope that he will clear up just what the Ada front-end needs from the rest of the compiler as far as asynchronous exceptions are concerned. >> gcc Ada turns signals into exceptions. As far as I know it does this >> completely asynchronously, and the fact that LLVM doesn't support this >> is rather bad as far as Ada is

On Jun 14, 2011, at 10:27 AM, Duncan Sands wrote: > Hi Chris, I've CC'd Eric Botcazou in the hope that he will clear up just what > the Ada front-end needs from the rest of the compiler as far as asynchronous > exceptions are concerned. > >>> gcc Ada turns signals into exceptions. As far as I know it does this >>> completely asynchronously, and the fact

From: Bradley Smith <brad at brad-smith.co.uk> This patch is from http://git.brad-smith.co.uk/?p=avr32/klibc.git;a=summary It squashes together and includes those commits: * Fix ld flags such that shared builds actually run. * Fix setjmp. * Fix sigaction/sigrestorer. * Tidy everything up. * Fix lseek mess. Cc: H?vard_Skinnemoen <hskinnemoen at gmail.com> Cc: Hans-Christian Egtvedt

Hi Florian, I understand you want to discuss the x86_64 micro-architecture levels only in this thread, but it would be nice to have a similar discussion for other architectures. One thing that wasn't clear to me from this proposal is how the glibc dynamic loader checks for the CPU feature flags. This is important for valgrind since it can communicate those through different means. cpuid

According to 6.3.1.3/3 of the C standard (I didn't check C++): "3 Otherwise, the new type is signed and the value cannot be represented in it; either the result is implementation-defined or an implementation-defined signal is raised." I *think* that means that IF a signal is raised then the signal raised could be one that you can't guarantee to be able to return from

Like this: llvm[1]: Compiling Signals.cpp for Debug build In file included from Signals.cpp:33: Win32/Signals.inc:262: error: `sys' has not been declared Win32/Signals.inc: In function `void AddSignalHandler(void (*)(void*), void*)': Win32/Signals.inc:266: error: `KillSigs' was not declared in this scope Win32/Signals.inc:266: error: `KillSigsEnd' was not declared in this scope

On Mar 8, 2009, at 4:21 AM, Lennart Augustsson wrote: > Like this: > > llvm[1]: Compiling Signals.cpp for Debug build > In file included from Signals.cpp:33: > Win32/Signals.inc:262: error: `sys' has not been declared > Win32/Signals.inc: In function `void AddSignalHandler(void (*) > (void*), void*)': > Win32/Signals.inc:266: error: `KillSigs' was not declared

Hello! I'm trying to work with virt-manager but getting SIGTRAP signal. It is done with gdb under MinGW32 on Windows 7 64-bit. I have Python 2.7.8. 32-bit. As I can see from backtrace ( http://pastebin.com/JhN6XgYb ), there is something wrong with libvirtmod.pyd. Also I couldn't find how to solve " typelib for AppIndicator3" error. So I try to debug libvirt-python. For doing

[test] comment = VFS TEST path = /data writeable = yes browseable = yes vfs objects = example:example1 example example:test example1: parameter = 1 example: parameter = 5 test: parameter = 7 for example, when change the example1: parameter = 2, how to change or update the already constructed handler. ???: Liujun (A) ????: 2013?2?25? 20:59 ???: 'samba at lists.samba.org' ??: how to

On Wed, 19 Apr 2006 19:28:34 +0100 Simon Burton <simon at arrowtheory.com> wrote: > > >From what I remember, this is a bug in debian libc: > some floating point flags are set incorrectly causing SIGFPE. > Can't find the bug report ATM. Oh, it just showed up on numpy-discussion: http://sources.redhat.com/bugzilla/show_bug.cgi?id=10 """ #include

On Fri, Jul 31, 2015 at 5:15 AM, Karl Skomski <karl at skomski.com> wrote: > Would it make sense to add the possibility to print a stacktrace also on > SIGFPE and not only on SIGSEGV or SIGBUS? > Yes, under a separate flag (handle_sigfpe=1). I think it's fine to have this flag on by default. Would you like to contribute a patch? > Only noticed that LibFuzzer doesn't

Just a quick question... I've been attempting to trap floating point badness by setting up a SIGFPE handler. However, I'm not seeing it trigger, even for simple test code that forces division by zero. I'm generating bitcode with llvm-gcc and then executing it with a (modified) version of the jitter, for reference. Is there any arcane magic necessary to turn on SIGFPE

Commenting out the Hello transformation I get these link errors: llvm[2]: Linking Debug Shared Library LTO.dll c:/DOCUME~1/1312888/Desktop/Workspace/llvm/llvm-top/Debug/lib/libLLVMSystem.a(Signals.o): In function `Z28LLVMUnhandledExceptionFilterP19_EXCEPTION_POINTERS': c:/DOCUME~1/1312888/Desktop/Workspace/llvm/llvm-top/lib/System/Win32/Signals.inc:164: undefined reference to

On Thu, 2017-05-18 at 09:27 +0200, Andrea Venturoli via samba wrote: > On 05/17/17 21:14, Andrew Bartlett wrote: > > > What is your platform > > FreeBSD 10.3/amd64. > > > > > and what is signal 4 on your platform? > > It is SIGILL on x86_64 linux. > > I believe signals are more or less standard across all Unices... anyway > it's SIGILL on

On Thu, 20 Apr 2006, Simon Burton wrote: >>> From what I remember, this is a bug in debian libc: >> some floating point flags are set incorrectly causing SIGFPE. >> Can't find the bug report ATM. > > Oh, it just showed up on numpy-discussion: > http://sources.redhat.com/bugzilla/show_bug.cgi?id=10 > > """ > #include <fenv.h> > void

Okay. Got to the next bit pretty quickly.: Breakpoint 4, auth_settings_read (service=0x0, pool=0x4104b020, output_r=0x7fdfffff6d0) at auth-settings.c:522 522 input.module = "auth"; (gdb) n 523 input.service = service; (gdb) n 524 if (master_service_settings_read(master_service, &input, (gdb) s Program received signal SIGTRAP, Trace/breakpoint trap. Cannot remove breakpoints

The parts of klibc specific to the i386 architecture. Signed-off-by: H. Peter Anvin <hpa at zytor.com> --- commit bd0599e5290ca1a16bb7a68f7c362d395c612eb3 tree 8f33afdd02a14c22e7a3984da2bad13184e3f729 parent 84f6a72f42cf41e32daa59871a0b5424572093e4 author H. Peter Anvin <hpa at zytor.com> Sun, 25 Jun 2006 16:58:21 -0700 committer H. Peter Anvin <hpa at zytor.com> Sun, 25 Jun

On Jun 14, 2011, at 2:11 AM, Duncan Sands wrote: > gcc Ada turns signals into exceptions. As far as I know it does this > completely asynchronously, and the fact that LLVM doesn't support this > is rather bad as far as Ada is concerned. That said, the Ada front-end You're saying that it turns asynch signals like SIGHUP (which can occur on any machine instruction) into signals?