similar to: ASAN not finding any bugs?

Hello Alex, Thanks for the hint. It was actually not the -O flag that created the problem. But it pointed me in the right direction, when I passed -fno-experimental-new-pass-manager it started to show the error. My guess is that the new pass manager is more aggressive in removing UB? Thanks, Tobias On Mon, Feb 3, 2020 at 5:29 PM Alex Brachet-Mialot <alexbrachetmialot at gmail.com> wrote:

I'm trying to compile the source for Dovecot 2.0.2 on a Solaris 10 SPARC machine. > uname -a SunOS ommtca013 5.10 Generic_138888-07 sun4v sparc SUNW,Sun-Blade-T6300 Solaris > cat /etc/release Solaris 10 10/08 s10s_u6wos_07b SPARC I've installed the following binaries from sunfreeware for dovecot 1.1 to use with 2.0.2 gcc-3.4.6-sol10-sparc-local

I'm not seeing how to set this path option? Here is what I get using vesamenu.c32 as an example when moved to a directory outside of the build. The current syslinux 4.06 has all the files in the same directory which is at the root of the cd. ldd vesamenu.c32 linux-gate.so.1 => (0xb77c5000) ../../com32/libutil/libutil_com.c32 => not found ../../com32/lib/libcom32.c32 => not found

I have a raid-z zfs filesystem with 3 disks. The disk was starting have read and write errors. The disks was so bad that I started to have trans_err. The server lock up and the server was reset. Then now when trying to import the pool the system panic. I installed the last Recommend on my Solaris U3 and also install the last Kernel patch (120011-14). But still when trying to do zpool import

http://dovecot.org/releases/1.1/dovecot-1.1.11.tar.gz http://dovecot.org/releases/1.1/dovecot-1.1.11.tar.gz.sig Hopefully this v1.1 release will last a few months. - IMAP: PERMANENTFLAGS list didn't contain \*, causing some clients not to save keywords. - dbox: INTERNALDATE and save date was returned wrong for converted maildir files. - auth: Using "username" or

http://dovecot.org/releases/1.1/dovecot-1.1.11.tar.gz http://dovecot.org/releases/1.1/dovecot-1.1.11.tar.gz.sig Hopefully this v1.1 release will last a few months. - IMAP: PERMANENTFLAGS list didn't contain \*, causing some clients not to save keywords. - dbox: INTERNALDATE and save date was returned wrong for converted maildir files. - auth: Using "username" or

Hi Igor, not sure if that will work, but have you tried lli -jit-kind=orc-lazy ? The default is still MCJIT: https://github.com/llvm/llvm-project/blob/master/llvm/tools/lli/lli.cpp#L88 On 13/01/2020 19:07, David Blaikie via llvm-dev wrote: > (+Lang for JIT/interpreter questions) > > On Sun, Jan 5, 2020 at 5:00 PM Igor Gomon via llvm-dev > <llvm-dev at lists.llvm.org

Hello, I am new to LLVM and what I am trying to do is to get a very simple “hello-world” C++ program to compile to LLVM IR and then to run it using lli tool. So here is the program code (hello.cpp): #include <iostream> int main (int argc, char *argv[]) { std::cout << "Hello World!\n"; return 0; } Below are the steps I do to achieve that goal: 1. clang++.exe

I've been using the nifty: DEBUG(errs() << "Here is the state of things:\n"); style of optional logging, but ran into an issue where I want to dump a table of information. The problem is getting the columns to line up, since the raw_ostream methods write numbers as variable length. I've worked up a patch that adds two new methods to raw_ostream: /// write_hex -

Hi Everyone, When I compile a program with clang with debug symbols enabled and I try to run it using the JIT (lli) I get the following error message. I am running on Lion (10.7.4). Thanks. George >> pseudo instructions should be removed before code emission UNREACHABLE executed at /Users/JD/Software/llvm3.1/llvm-3.1.src/lib/Target/X86/X86CodeEmitter.cpp:736! 0 lli

My dovecot/auth process crashes several times a minute, sometimes at the same second, sometimes randomly. I?ve turned on auth_debug and been pouring over everything trying to see if I can see what is going on but I can?t find anything. I?m running OS X Server 10.9 and dovecot 2.2.5. I can?t say for sure, but it looks to me like the crashed process doesn?t even save anything to mail-debug.log

On Dec 1, 2011, at 9:09 AM, Chris Lattner wrote: > > On Dec 1, 2011, at 8:46 AM, Dan Gohman wrote: > >> >> On Nov 30, 2011, at 10:49 PM, Chris Lattner wrote: >> >>> >>> On Nov 29, 2011, at 3:21 PM, Dan Gohman wrote: >>> >>>> >>>> A natural reaction to this problem is to think that LLVM IR is so nice

Hi Stefan, I just tried the -jit-kind=orc-lazy with lli executable and it solves the problem on Ubuntu 18.04 (still does not work on Windows 10). But this solution is good enough for me now. Thanks again for your help! -- Best Regards, Igor ________________________________ From: Igor Gomon <giv_ua at hotmail.com> Sent: Tuesday, January 14, 2020 7:38 PM To: Stefan Gränitz

I just found this in my logs. Any idea? --8<---------------cut here---------------start------------->8--- 12/4/12 12:33:43.831 PM dovecot[2660]: indexer-worker(dave): Panic: file mailbox-list-fs.c: line 156 (fs_list_get_path): assertion failed: (mailbox_list_is_valid_pattern(_list, name)) 12/4/12 12:33:43.831 PM dovecot[2660]: indexer-worker(dave): Error: Raw backtrace: 2

Hello, I hope that I am posting the correct list with this question. I have been trying to get VGA passthrough working on my system for some time now without success. I do not have the system with me right now, so I will not be able to provide any logs or error messages right now. I will be able to to do so in a couple of hours. I have a VT-d enabled system (Motherboard and CPU) on which I wish

Hello, I hope that I am posting the correct list with this question. I have been trying to get VGA passthrough working on my system for some time now without success. I do not have the system with me right now, so I will not be able to provide any logs or error messages right now. I will be able to to do so in a couple of hours. I have a VT-d enabled system (Motherboard and CPU) on which I wish

Dan Gohman <gohman at apple.com> writes: > In a world where signed add overflow returns undef, c could be any of > 0x0000000000000000 > 0x0000000000000001 > 0x0000000000000002 > ... > 0x000000007fffffff > or > 0xffffffff80000000 > 0xffffffff80000001 > 0xffffffff80000002 > ... > 0xffffffffffffffff > however it can't ever be

On May 18, 2012, at 11:50 AM, Nick Kledzik <kledzik at apple.com> wrote: > I've been using the nifty: > DEBUG(errs() << "Here is the state of things:\n"); > style of optional logging, but ran into an issue where I want to dump a table of information. The problem is getting the columns to line up, since the raw_ostream methods write numbers as variable length.

Dear LLVM devs, I've noticed that LLVM's assembler (and hence clang) doesn't generate debug data when assembling, even when run with "-g". Users can add their own CFI/line number data with assembler directives. But GDB ignores the line number data if you don't have a DIE in the .debug_info section which identifies the compilation unit. (I'm not an expert on GDB, but

Hey guys, Frederic is introducing the expression dumping support and in the interests of tersity is skipping the "DW_" in every "DW_OP" (heck, we could even skip the "OP" given the context - nothing else textual can appear there, right?) Any thoughts on skipping the "DW_" (maybe even the AT/TAG/FORM too) in the rest of dwarfdump? (skipping the AT/TAG (FORM