search for: foisting

On Oct 11, 2013, at 12:07 PM, Eric Christopher <echristo at gmail.com> wrote: >> >> Since we don't have ODR, we may have macros defined differently for a struct >> in a .h file, >> thus having two versions of the struct from two different CU. It seems that >> we can't assume >> structs with the same name and defined in the same file/line/column

Hi Eric, This makes total sense, thanks. One thing though; it seems a lot of functionality is being foisted onto the client. This is all well and good, but it seems that clients are expected to reinvent the wheel quite a bit for no real purpose - an example is the implementation of getPointerToNamedFunction, allocate{Code,Data}Section and invalidateInstructionCache in lli.cpp. Many clients will

So this is likely just an accident rather than on purpose. There's totally room for that to happen, but it'll be the job of the client and not MCJIT itself. Basically whomever should call dlopen if they want to and it's the problem of the client application (which could be lli as the canonical mcjit example) to link in the correct bits. Make sense? If you can see a use case in

On Jun 2, 2017, at 5:05 AM, hw <hw at gc-24.de> wrote: > > Warren Young wrote: >> >> There are various options. We use mod_fcgid + Plack here. > I need to look into that when I have time. I wonder if it wouldn?t have been faster to just backport the app to Perl 5.16? How hard could it be? It?s not like Perl 5.16 is a hopelessly lame and incapable language. The

Hi! I've installed the newest wine on my fedora (by yum install wine) And I've installed Zbrush 3.5 r3 on it. when I'm trying to execute: wine "c:\programy\zbrush35r3\zbrush.exe" I'm getting: Trying to load PE image for unsupported architecture (I386) Trying to load PE image for unsupported architecture (I386) What should I do? are there any versions of wine? my yum

> rab45+ at pitt.edu wrote: >> Jerry, >> >> Here are the two R packages. >> >> Thanks. >> >> Rick > All the fortran codes compile OK so the problem is invoking the compiler > you > want. One approach which is a work around is to rename the gfortran > executable > to somthing else like gfortran-save and create a link called gfortran that

Warren Young wrote: > On Jun 2, 2017, at 5:05 AM, hw <hw at gc-24.de> wrote: >> >> Warren Young wrote: >>> >>> There are various options. We use mod_fcgid + Plack here. >> I need to look into that when I have time. > > I wonder if it wouldn?t have been faster to just backport the app to Perl 5.16? How hard could it be? It?s not like Perl 5.16

> > Since we don't have ODR, we may have macros defined differently for a struct > in a .h file, > thus having two versions of the struct from two different CU. It seems that > we can't assume > structs with the same name and defined in the same file/line/column are the > same. > Ah right sorry, I remember this. Also, macros are evil, just ask the modules guys :)

On May 24, 2017, at 9:38 AM, hw <hw at gc-24.de> wrote: > > Warren Young schrieb: >> On May 24, 2017, at 7:05 AM, hw <hw at gc-24.de> wrote: >>> apache uses mod_perl >> >> mod_perl was dropped from Apache in 2.4, and Red Hat followed suit with RHEL 7. > > What is it using instead? There are various options. We use mod_fcgid + Plack here. And

Hi all, Is there a function to open a script file from the command line? I have several students who are Mac users and when they open up a script file it does not send commands to the console, and unfortunately I don't know how to solve this problem since I am not a Mac user. I have looked over the FAQ for Mac users, but didn't see a reference to the problem. I think they are both

Hi I noticed in a post that Timo might start work on a LDA Great! If so, here is something I would really like included. Support for PAM There is quite a lengthy reason behind this. In my organisation, user accounts are created on ldap. It is up to the services to create home directories whenever the user first uses them. For instance, Samba will do this the first time they connect to their

On Fri, Oct 11, 2013 at 11:48 AM, Eric Christopher <echristo at gmail.com>wrote: > > With C++'s ODR, we are able to unique C++ types by using type > identifiers to > > refer to types. > > Type identifiers are generated by C++ mangler. What about languages > without > > ODR? Should we unique C types as well? > > > > We can, but the identifier