similar to: [LLVMdev] conditional flow resulting in "Instruction does not dominate all uses!"

On 4 November 2013 02:31, Henrique Santos <henrique.nazare.santos at gmail.com> wrote: > But the incoming value from the landing pad will always be null, won't it? > If so, just iterate through the predecessors and add the terminator as the > incoming value if it's an invoke instruction and add the null value it's > not. > Won't that work? > Note that the

Well, what I had in mind was actually something like the following: entry: result0 = invoke func0 to defer_block unwind landing0 landing0: landingpad result1 = invoke func1 to defer_block unwind landing1 landing1: landingpad br defer_block defer_block: result = phi [ result0, entry ], [ result1, landing0 ], [ null, landing1 ] ... This doesn't have landing pads with multiple

On 03/11/13 12:16, Henrique Santos wrote: > You could try placing a phi node at "defer_block" with incoming value > "result" > when the incoming block is "entry", and do the same for "null" and > "landing". > Then, instead of loading "result", you load the value given by the newly > created phi. That seems like the

But the incoming value from the landing pad will always be null, won't it? If so, just iterate through the predecessors and add the terminator as the incoming value if it's an invoke instruction and add the null value it's not. Won't that work? On Mon, Nov 4, 2013 at 2:22 AM, edA-qa mort-ora-y <eda-qa at disemia.com>wrote: > On 03/11/13 12:16, Henrique Santos wrote:

On 4 November 2013 08:19, Henrique Santos <henrique.nazare.santos at gmail.com> wrote: > Well, what I had in mind was actually something like the following: > > entry: > result0 = invoke func0 to defer_block unwind landing0 > > landing0: > landingpad > result1 = invoke func1 to defer_block unwind landing1 > > landing1: > landingpad > br

If you're talking about the IR, then I don't think so. It seems like perfectly valid. H. On Mon, Nov 4, 2013 at 2:25 PM, Rafael Espíndola <rafael.espindola at gmail.com > wrote: > On 4 November 2013 08:19, Henrique Santos > <henrique.nazare.santos at gmail.com> wrote: > > Well, what I had in mind was actually something like the following: > > > >

Hiall, I want to give the action of a form an additional parameters but can''t figure out how to do it. My code looks like this <%= start_form_tag :action => ''create'', next_step => true %> <%= render :partial => ''user_form'' %> <%= render :partial => ''community_form'' %> <%= submit_tag

I can't seem to find a definitive answer on this, and I really don't want to risk breaking a production server to find out; so I am going to try asking this here, and maybe anyone else in the same situation searching the archives sometime in future will find the answer I get. Can you use variables in the target of a GoTo() statement? What I am specifically thinking of is this;

I've been adding some new flow statements to my compiler and realize the easiest/laziest way to produce the DAG is just to store a flow variable and end blocks with a "switch" branch. It appears the optimizers do a fine job of unwinding the nonsense, reducing the conditions, and even expanding the trailing paths. For example, I terminate my blocks with a logical switch like this:

I am using dovecot-lda from cvs (checked out on september the 21st) and dovecot 1.0alpha2 (not yet upgraded ok). I have a strange feeling about "redirect" feature. Let's see two sieve scripts examples: # ex1 require ["fileinto", "vacation"]; if header :is ["blabla"] "blabla" { fileinto "blabla"; } redirect

Hi Timo I've been seeing data corruption in the lda when forwarding mail. I think it's due to confused file pointers. (this is all maildirs on nfs) Anyway the following patch fixes it, and also looks a bit more like the old dovecot-lda module, by getting the Return-Path header before getting the input stream: Index: mail-send.c

Hi edA-qa mort-ora-y, On 17/04/13 21:27, edA-qa mort-ora-y wrote: > I've been adding some new flow statements to my compiler and realize the > easiest/laziest way to produce the DAG is just to store a flow variable > and end blocks with a "switch" branch. It appears the optimizers do a > fine job of unwinding the nonsense, reducing the conditions, and even > expanding

The function "substitute" seems to fail to make a genuine substitution, although the printed verision seems fine. Here is an example. > m <- substitute(Y <- function(x) FUN(x+1), + list(Y = as.name("y"), FUN = as.name("sin"))) > m y <- function(x) sin(x + 1) > eval(m) > y function(x) FUN(x+1) However the story doesn't end there. The

I'm using exim4 to deliver into dovecot 1.1, and using plus-addressing to deliver mailing lists directly to appropriate folders in my "lists" mailbox. I created a file called /folder-map.lists that looks like ## folder-map.lists dovecot: Dovecot lpedge: Linux PowerEdge ... and so on. So mail to lists-lpedge at jay.fm goes to the "Linux PowerEdge" folder. The one

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello, I have a small Sieve script that tries to use vacation that segfaults. The script is the one from http://wiki.dovecot.org/LDA/Sieve. When I change the email address (I changed the local part into "skai"), hence, vacation is skipped, the mail is delivered without any problem. ==== script start require ["fileinto",

While YAJL mostly works fine, it did not see any active development in the last 3 years. OTOH, Jansson is another JSON C implementation, with a very liberal license, and a much nicer API. Hence, switch all of libguestfs from YAJL to Jansson: - configure checks, and buildsystem in general - packages pulled in the appliance - actual implementations - contrib scripts - documentation This also

While YAJL mostly works fine, it did not see any active development in the latest 3 years. OTOH, Jansson is another JSON C implementation, with a very liberal license, and a much nicer API. Hence, switch all of libguestfs from YAJL to Jansson: - configure checks, and buildsystem in general - packages pulled in the appliance - actual implementations - contrib scripts - documentation This also

Hi, recently, there was a discussion in the development list of libvirt on switching to a different JSON library than YAJL [1]. Since we use YAJL, and the points there IMHO apply to libguestfs as well, I decided to give a try in switching to Jansson [2]. The result IMHO is nice, with the additional APIs of Jansson that simplify some of our code. Unlike with YAJL, I did not set a minimum

$ gdb /usr/lib/dovecot/lmtp core_lmtp.48883.nihlus.leuxner.net GNU gdb (GDB) 7.4.1-debian Copyright (C) 2012 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show

Hi, recently, there was a discussion in the development list of libvirt on switching to a different JSON library than YAJL [1]. Since we use YAJL, and the points there IMHO apply to libguestfs as well, I decided to give a try in switching to Jansson [2]. The result IMHO is nice, with the additional APIs of Jansson that simplify some of our code. Unlike with YAJL, I did not set a minimum