Displaying 20 results from an estimated 500 matches similar to: "[IA64]: noreturn cannot be used if function may return"
2006 Jun 20
1
Re: [Xen-ia64-devel] Weekly benchmark results [ww24]
==================
STATUS
==================
I do the heavy load test of create/destroy.
CREDIT scheduler(cshed_schedule) checks BUG_ON(!vcpu_running) at the end of code.
It makes error.
The reason is that
atomic_inc(&v->pausecnt)@vcpu_pause() is called without lock.
(spin_lock(&schedule_data[cpu].schedule_lock))
This lock-less "pausecnt" makes vcpu_running state changing
2005 Apr 02
1
[PATCH] VMX support for MMIO/PIO in VM8086 mode
Memory mapped and port I/O is currently broken under VMX when the
partition is running in VM8086 mode. The reason is that the instruction
decoding support uses 32-bit opcode/address decodes rather 16-bit
decodes. This patch fixes that. In addition, the patch adds support for
the "stos" instruction decoding because this is a frequently used way
to clear MMIO areas such as the screen.
As
2005 Nov 03
0
[PATCH] vmx-platform-vmread.patch
Simplified vmx_platform.c by removing obsolete code and redundant vmread''s.
Signed-Off-By: Leendert van Doorn <leendert@watson.ibm.com>
diff -r 9cdfcecf4968 xen/arch/x86/vmx_platform.c
--- a/xen/arch/x86/vmx_platform.c Wed Nov 2 16:29:32 2005
+++ b/xen/arch/x86/vmx_platform.c Wed Nov 2 21:12:02 2005
@@ -366,20 +366,15 @@
return DECODE_success;
}
-static int
2008 Jun 10
0
[PATCH] xen-netfront: fix xennet_release_tx_bufs().
After restore on ia64 xen domain, kernel panics as follows.
This patch fixes it.
union skb_entry assumes sizeof(link->skb, pointer) ==
sizeof(list->link, unsigned).
However this isn't true on ia64. So make link type unsigned long.
And introduced two accesor.
kernel unaligned access to 0xe0000000000000bd, ip=0xa0000001004c2ca0
xenwatch[14]: error during unaligned kernel access
-1 [1]
2008 Jun 10
0
[PATCH] xen-netfront: fix xennet_release_tx_bufs().
After restore on ia64 xen domain, kernel panics as follows.
This patch fixes it.
union skb_entry assumes sizeof(link->skb, pointer) ==
sizeof(list->link, unsigned).
However this isn't true on ia64. So make link type unsigned long.
And introduced two accesor.
kernel unaligned access to 0xe0000000000000bd, ip=0xa0000001004c2ca0
xenwatch[14]: error during unaligned kernel access
-1 [1]
2008 Jun 10
0
[PATCH] xen-netfront: fix xennet_release_tx_bufs().
After restore on ia64 xen domain, kernel panics as follows.
This patch fixes it.
union skb_entry assumes sizeof(link->skb, pointer) ==
sizeof(list->link, unsigned).
However this isn't true on ia64. So make link type unsigned long.
And introduced two accesor.
kernel unaligned access to 0xe0000000000000bd, ip=0xa0000001004c2ca0
xenwatch[14]: error during unaligned kernel access
-1 [1]
2005 Jun 30
0
[PATCH][2/10] Extend the VMX intercept mechanism to include mmio as well as portio.
Extend the VMX intercept mechanism to include mmio as well as portio.
Signed-off-by: Yunhong Jiang <yunhong.jiang@intel.com>
Signed-off-by: Xiaofeng Ling <xiaofeng.ling@intel.com>
Signed-off-by: Arun Sharma <arun.sharma@intel.com>
diff -r febfcd0a1a0a -r 9a43d5c12b95 xen/include/asm-x86/vmx_platform.h
--- a/xen/include/asm-x86/vmx_platform.h Thu Jun 30 03:20:48 2005
+++
2012 Nov 29
0
[LLVMdev] noreturn attribute on a call instruction vs noreturn on afunction
You can use CallInst::hasFnAttr(). It checks for attributes in the
instruction and in the function decl.
http://llvm.org/docs/doxygen/html/Instructions_8cpp_source.html#l00345
Nuno
----- Original Message -----
> Hi,
>
> Building the following C code I get a call instruction that has no
> noreturn
> attribute, while the function itself does have it.
>
> void foo(void **b)
2012 Nov 28
0
[LLVMdev] noreturn attribute on a call instruction vs noreturn on a function
Hi Kostya,
On 28/11/12 14:47, Kostya Serebryany wrote:
> Hi,
>
> Building the following C code I get a call instruction that has no noreturn
> attribute, while the function itself does have it.
>
> void foo(void **b) {
> __builtin_longjmp(b, 1);
> }
>
>
> define void @_Z3fooPPv(i8** %b) noreturn nounwind uwtable {
> entry:
> %0 = bitcast i8** %b to i8*
2012 Nov 28
4
[LLVMdev] noreturn attribute on a call instruction vs noreturn on a function
Hi,
Building the following C code I get a call instruction that has no noreturn
attribute, while the function itself does have it.
void foo(void **b) {
__builtin_longjmp(b, 1);
}
define void @_Z3fooPPv(i8** %b) noreturn nounwind uwtable {
entry:
%0 = bitcast i8** %b to i8*
tail call void @llvm.eh.sjlj.longjmp(i8* %0)
2010 Jun 05
1
[LLVMdev] Why UnreachableInst instruction is required when the last call has NoReturn flag?
Looks like these two things duplicate each other.
Yuri
2010 Jul 15
2
[LLVMdev] Why clang++ doesn't set 'noreturn' flag on declarations of __cxa_throw and _Unwind_Resume_or_Rethrow ?
When I compile some code with the near-trunk clang++ I get this:
...
tail call void @_Unwind_Resume_or_Rethrow(i8* %exn2) noreturn
unreachable
...
declare void @_Unwind_Resume_or_Rethrow(i8*)
...
Same with __cxa_throw. 'noreturn' is missing on declarations.
This seems to be a bug.
Also can _Unwind_Resume_or_Rethrow actually return? When I run some
simple exception code in JIT I
2010 Jul 16
0
[LLVMdev] Why clang++ doesn't set 'noreturn' flag on declarations of __cxa_throw and _Unwind_Resume_or_Rethrow ?
On Jul 15, 2010, at 3:31 PM, Yuri wrote:
> When I compile some code with the near-trunk clang++ I get this:
Please send clang-specific questions to cfe-dev at cs.uiuc.edu.
> ...
> tail call void @_Unwind_Resume_or_Rethrow(i8* %exn2) noreturn
> unreachable
> ...
> declare void @_Unwind_Resume_or_Rethrow(i8*)
> ...
>
> Same with __cxa_throw. 'noreturn' is
2010 Jul 16
2
[LLVMdev] Why clang++ doesn't set 'noreturn' flag on declarations of __cxa_throw and _Unwind_Resume_or_Rethrow ?
On Jul 15, 2010, at 5:51 PM, John McCall wrote:
>> Also can _Unwind_Resume_or_Rethrow actually return? When I run some
>> simple exception code in JIT I see that this function actually returns
>> and then SEGVs.
>
> I have no idea what system you're on, but _Unwind_Resume_or_Rethrow really
> isn't allowed to return.
>
It's not. But if the unwind
2010 Jul 16
0
[LLVMdev] Why clang++ doesn't set 'noreturn' flag on declarations of __cxa_throw and _Unwind_Resume_or_Rethrow ?
On 07/15/2010 18:30, Bill Wendling wrote:
> It's not. But if the unwind library can't handle something, then the _Unwind_Resume_or_Rethrow could fall out of the function (it would assert in debug mode). Darwin's implementation of _URoR in libunwind does this.
>
>
Isn't unwind library supposed to call terminate() every time it can't
handle something?
Yuri
2010 Jul 16
1
[LLVMdev] Why clang++ doesn't set 'noreturn' flag on declarations of __cxa_throw and _Unwind_Resume_or_Rethrow ?
On Jul 15, 2010, at 6:52 PM, Yuri wrote:
> On 07/15/2010 18:30, Bill Wendling wrote:
>> It's not. But if the unwind library can't handle something, then the _Unwind_Resume_or_Rethrow could fall out of the function (it would assert in debug mode). Darwin's implementation of _URoR in libunwind does this.
>>
> Isn't unwind library supposed to call terminate() every
2013 Aug 01
0
[LLVMdev] Fwd: can i avoid saving CSRs for functions with noreturn
Hi
(Adding the list back in).
On 1 August 2013 08:44, Liu Xin <navy.xliu at gmail.com> wrote:
> i know where to calculate CSRs. the additional stack space is calculated in
> PEI::calculateCalleeSavedRegisters. the real instructions are inserted in
> insertCSRSpillsAndRestores.
> my point is why llvm code honor 'naked' but does not 'noreturn' for CSR.
And to me
2006 Nov 21
1
rsync v2.6.9: small patch fixing NORETURN failures
Hello,
as of gcc v2.7.2.1, the noreturn attribute needs to be given
*after* the prototype declaration and not before, but for
gcc v3.x, things changed for this attribute again, since
gcc v2.5.x did it the way, newer gcc versions prefer it...
I've applied a small unified diff, fixing this stuff.
THX for listening.
CU Tom.
(Thomas M.Ott)
Germany
-------------- next part --------------
---
2017 Feb 14
0
[PATCH v2 1/2] GCC 7: Add __attribute__((noreturn)) to some usage functions which call exit.
This happens with GCC 7.0.1. The errors were all of the form:
qemu-speed-test.c: In function 'main':
qemu-speed-test.c:153:7: error: this statement may fall through [-Werror=implicit-fallthrough=]
usage (EXIT_SUCCESS);
^~~~~~~~~~~~~~~~~~~~
qemu-speed-test.c:155:5: note: here
default:
^~~~~~~
---
builder/index-validate.c | 2 +-
2013 Aug 01
2
[LLVMdev] can i avoid saving CSRs for functions with noreturn
hi, list,
i am making a llvm compiler for shader-like programs. as we known, shader
programs are short and have less function calls. i found that i have to
save/restore callee-saved register(CSR) in prolog and epilog. because I
can violate ABI from driver(c code) and shader, i plan to append the
attribute 'noreturn' to all shader functions.
in PrologEpilogInserter.cpp, you can find that