Displaying 20 results from an estimated 3000 matches similar to: "best way to represent this pseudocode in LLVM IR?"
2019 Feb 09
2
how experimental are the llvm.experimental.vector.reduce.* functions?
I'm interested in using @llvm.experimental.vector.reduce.smax/umax to
implement runtime overflow checking for vectors. Here's an example
checked addition, without vectors, and then I'll follow the example with
what I would do for checked addition with vectors.
Frontend code (zig):
export fn entry() void {
var a: i32 = 1;
var b: i32 = 2;
var x = a + b;
}
LLVM IR code:
2019 Feb 09
2
how experimental are the llvm.experimental.vector.reduce.* functions?
The IR update to allow vector types was here:
https://reviews.llvm.org/D57090
...we didn't update the docs at that time because it was not clear what the
backend would do with that, but that might've changed with some of the more
recent patches.
On Sat, Feb 9, 2019 at 1:42 AM Craig Topper via llvm-dev <
llvm-dev at lists.llvm.org> wrote:
> I don't think I understand your
2019 Feb 09
2
how experimental are the llvm.experimental.vector.reduce.* functions?
On Sat, Feb 9, 2019 at 6:25 PM Simon Pilgrim <llvm-dev at redking.me.uk> wrote:
> The add/sub (+mul) overflow intrinsics are being updated to support
> vectors to match the related add/sub saturation intrinsics. We haven't
> updated the docs yet as legalization, vectorization and various minor bits
> of plumbing still need to be finished before it can be officially supported
2018 Jun 27
2
can debug info for coroutines be improved?
I'm going to show the same function, first normally, and then as a
coroutine, and show how gdb can see the variable when it's a normal
function, but not when it's a coroutine. I'd like to understand if this can
be improved.
I'm trying to debug a real world problem, but the lack of debug info on
variables in coroutines is making it difficult. Should I file a bug? Is
this a
2019 Feb 09
2
how experimental are the llvm.experimental.vector.reduce.* functions?
Something like this should work I think.
; ModuleID = 'test.ll'
source_filename = "test.ll"
define void @entry(<4 x i32>* %a, <4 x i32>* %b, <4 x i32>* %x) {
Entry:
%tmp = load <4 x i32>, <4 x i32>* %a, align 16
%tmp1 = load <4 x i32>, <4 x i32>* %b, align 16
%tmp2 = add <4 x i32> %tmp, %tmp1
%tmpsign = icmp slt <4 x
2013 Mar 29
1
Asterisk 11 - Change CDR in hangup exten [Was: CDR values changed in hangup handler not saved]
2013/3/29 Julian Lyndon-Smith <asterisk at dotr.com>
> check out the endbeforehexten option in cdr.conf
>
> this needs to set to "yes"
>
> Julian
>
Unfortunately, this doesn't help.
Let's drop the hangup handler at the moment, and focus on the "saving to
file" part.
Then my issue is I can't update CDR value is hangup exten.
Here is a
1999 Oct 04
3
Detailed decoder pseudocode (was: Re: ETA?)
> > Which part?
>
> Well, my biggest problem is dealing with files. As you have mentioned
> that fill_buffer() is obsolete, what has replaced it? ogg_sync_buffer()
> didn't seem to be what I was looking for, as far as I can tell... am I
> headed in completely the wrong direction?
Ah, OK, I understand where you're headed now.
The libvorbis API is different than
2006 Dec 05
2
intro + specification remarks + some questions
hi everyone,
since about 10 days I've been working on an implementation of ogg vorbis
*decoder* from scratch, and I've got a few constructive remarks about
the specs and some questions.
--------------------------
First a question:
> 9.2.4. low_neighbor
>
> "low_neighbor(v,x)" finds the position n in vector [v] of the greatest
> value scalar element for which
2020 Apr 28
0
[PATCH v3 45/75] x86/dumpstack/64: Handle #VC exception stacks
From: Joerg Roedel <jroedel at suse.de>
Make the stack unwinder aware of the IST stacks for the #VC exception
handler.
Signed-off-by: Joerg Roedel <jroedel at suse.de>
---
arch/x86/include/asm/cpu_entry_area.h | 1 +
arch/x86/include/asm/sev-es.h | 13 ++++++++
arch/x86/include/asm/stacktrace.h | 4 +++
arch/x86/kernel/dumpstack_64.c | 47
2018 Mar 29
0
workaround for CoroSplit not spilling alloca?
My frontend is emitting an array (here called
%error_return_trace_addresses). You can see we take the address of the
first element and store it
; Function Attrs: nobuiltin noinline nounwind optnone
define internal fastcc i8* @failing(%StackTrace* nonnull, %Allocator*,
i16*) unnamed_addr #3 !dbg !273 {
Entry:
%error_return_trace_addresses = alloca [1 x i64], align 8
%error_return_trace =
2011 Sep 28
1
CentOS 6.0: iptables stacktrace with named chains > 28 chars
Hi,
I'm not sure where to ask this question, you, redhat or netfilter so I'll
ask you guys first, hoping you can redirect me where this post belongs.
I have an issue with my CentOS 6 box with named chains in iptables.
Apparently there is a builtin #define to limit chain names up to 30 chars,
but the test condition fails and iptables crashes with a stacktrace.
# cat /etc/redhat-release
2018 Apr 04
0
[Bug 13364] rsyncd clips trims relative symlinks outside of source tree
https://bugzilla.samba.org/show_bug.cgi?id=13364
--- Comment #3 from Chris Severance <samba.severach at spamgourmet.com> ---
>enable munge-symlinks. That way the client will get back the same out-of-tree symlink as it started with
This is a lousy option for backups. The only way to get my original links back
is to pull the restore through rsync. Restoring directly from the rsyncd server
2008 Sep 05
0
[LLVMdev] Demangling question
So I got tired of LLVM's PrintStackTrace() function only being able to
print mangled C++ names. I went ahead and wrote a demangler (shown
below), however there's one slight problem, which is that the output of
backtrace_symbols appears to be different on different platforms. In
order to use the cxxabi demangler, you need to provide it with the
portion of each line that contains the
2020 Aug 24
0
[PATCH v6 47/76] x86/dumpstack/64: Add noinstr version of get_stack_info()
From: Joerg Roedel <jroedel at suse.de>
The get_stack_info functionality is needed in the entry code for the #VC
exception handler. Provide a version of it in the .text.noinstr
section which can be called safely from there.
Signed-off-by: Joerg Roedel <jroedel at suse.de>
Link: https://lore.kernel.org/r/20200724160336.5435-47-joro at 8bytes.org
---
arch/x86/include/asm/stacktrace.h
2018 Feb 26
0
problem with moveSpillUsesAfterCoroBegin
Here's what this function is supposed to do:
// Move early uses of spilled variable after CoroBegin.
// For example, if a parameter had address taken, we may end up with the
code
// like:
// define @f(i32 %n) {
// %n.addr = alloca i32
// store %n, %n.addr
// ...
// call @coro.begin
// we need to move the store after coro.begin
in the
2016 Jun 30
0
Building LLVM under Cygwin32 fails
Googling indicates that cygwin doesn't have that functionality. Or, at
least, didn't in 2010, when someone asked about the same problem:
https://cygwin.com/ml/cygwin/2010-01/msg00596.html
"cygwin has only dlsym() not the SGI DL_info + dladdr() yet.
clang just needs it to get the path for the CIndex dll.
This should be possible with the code in the LLVM_ON_WIN32 section,
and convert
2016 Jun 30
3
Building LLVM under Cygwin32 fails
I am updating our out-of-tree copy of LLVM to track the head (revision
#272991 specifically).
I have it building successfully with VC++ 2013 and CMake v3.5.2 on Windows,
and with GCC v4.8.5 and CMake v3.5.2 on CentOS; but when I try building on
Windows using Cygwin32 I get the following build failures:
[ 4%] Building CXX object
lib/Support/CMakeFiles/LLVMSupport.dir/Signals.cpp.o
In file
2007 Jun 01
1
[CruiseControl] RubyOnRails build 6924.1 failed
The build failed.
CHANGES
-------
Revision 6924 committed by david on 2007-06-01 06:48:09
Added proper handling of arrays (closes #8537) [hasmanyjosh]
M /trunk/activesupport/test/core_ext/array_ext_test.rb
M /trunk/activesupport/CHANGELOG
M /trunk/activesupport/test/core_ext/hash_ext_test.rb
M /trunk/activesupport/lib/active_support/core_ext/array/conversions.rb
M
2007 Aug 22
1
C code generators
Dear R-helpers
Are there any established R packages that include a C code generator --
that generates new C language files and compiles them?
To be precise what I'm looking for is a process that takes text input in
some format (it might be pseudocode, fragments of C code, etc) and creates
a valid C language source file that can be compiled by R CMD COMPILE.
Ideally the procedure should also
2018 May 11
0
best way to represent function call with new stack in LLVM IR?
On 2018-05-11 02:28, Andrew Kelley via llvm-dev wrote:
> In the Zig frontend, we know at compile-time the entire call graph.
> This means we know stack size for all functions and therefore the
> upper bound stack usage.
>
> [snip]
> 1. Is there a way to accomplish this with existing LLVM API?
You should use the @llvm.stacksave and @llvm.stackrestore intrinsic.
It is only legal