search for: retrofitted

I am seeking advice. In your estimation, how difficult would it be to retrofit LLVM 3.2 with this body of improvements to instruction scheduling (and optionally, the loop vectorization as well). Would you have any suggestions for how best this might be achieved, i.e. the scope of the code required? Has anyone attempted this kind of retrofit? Thanks, Rick -------------- next part

Previously I had asked how to write then read back IR to/from a file. The write code looked like: LLVMContext ctx; SMDiagnostic diag; Module *m = ParseIRFile( "my_file", diag, ctx ); However, the code I'm trying to retrofit LLVM IR into passes me just a std::ostream&. How can I read IR from a std::ostream? I figured out how to use raw_os_ostream to adapt a

Hey all - does RHES4/CentOS4 beta contain a recent integration of Subversion? I've been holding off trying to retro-fit CentOS 3.x on our CVS server, hoping that the official channels aready had it in store for the future. Not that you *can't* retrofit, I was just uncomfortable upgrading so many stock packages. Anyone have it installed, can take a look for me? thx, -te -- Troy

Hi, we are experiencing significant performance degradation after live migration of hvm domains in Xen 4.0 (SLES11 SP1): after live migration the performance is dropping to less than 90%. I did a backport of cs 23420-23423 and the performance is okay now. I would like to request to include these changesets in 4.0 and 4.1. The backport is quite trivial, I can send patches if you are willing to

On Wed, 2017-06-07 at 11:23 -0500, Johnny Hughes wrote: > If you want to create a CentOS-7 variant that does not use systemd, > then start a Special Interest Group and create modified packages > to use something else instead ......., much like the this group did > with Debian: > > https://devuan.org/ > > In the case of CentOS-7 .. you don't need to create a whole new

So when puppetd crashes/whatever, and a pid file is left behind, SMF in Solaris will try restarting puppet, but fail. And then it sits there restarting it forever. I''m not sure if I can adjust the flap detection in SMF.. it isn''t disabling the service for "restarting too quickly" because it takes so long to start. Probably because I''m NFS-mounting ruby. The

On 6/7/2017 11:28 AM, Always Learning wrote: >> In the case of CentOS-7 .. you don't need to create a whole new >> distro, you can just petition the CentOS Project Board to create a >> Special Interest Group to get access to CentOS Project controlled >> resources to build packages (and get them rolled into our mirrors, >> etc.) to use something other than systemd.

I just downloaded and installed the source to 2.0.5a, and it worked perfectly. I really like the fact that everything by default goes under /usr/local/samba (I just did the ./configure; make; make install). The one thing I don't see is the start/stop/restart commands like I used to have in my Red Hat rpm installation: /etc/rc.d/init.d/smb restart It was a shellscript to read the .pid files,

On 06/07/2017 02:02 PM, John R Pierce wrote: > On 6/7/2017 11:28 AM, Always Learning wrote: >>> In the case of CentOS-7 .. you don't need to create a whole new >>> distro, you can just petition the CentOS Project Board to create a >>> Special Interest Group to get access to CentOS Project controlled >>> resources to build packages (and get them rolled

To say this first: This whole discussion about using virtregs until emit or having growable physregs is hard to argue without actually having experience trying to go either way. Problems when using virtregs throughout the backend until emit time: - The MC layer is using MCPhysReg (which is an uint16_t) and would need retrofitting to support virtregs - VirtRegs are assumed to have a definition,

On Tuesday, September 03, 2013 07:52:08 PM Richard W.M. Jones wrote: > Even better, there is a repo: https://github.com/mdbooth/guestconv Excellent. Thanks for the pointer. > Matt - can you push your latest commits, or is there a more canonical > repo that Mike can look at? The last changes in the repo seem to be from back in June. Is guestconv expected to completely replace virt-v2v

On Wed, Jan 25, 2017 at 08:42:34PM -0600, Eric Blake wrote: > +eg. NULL or -1. If the call to C<nbdkit_set_error> is omitted, then > +the value of C<errno> will be used instead. [...] > +/* Grab the appropriate error value. > + */ > +static int > +_get_error (void) > +{ > + int err = errno; > + int ret = tls_get_error (); > + > + if (!ret) > +

On Thursday, September 05, 2013 12:00:44 PM Matthew Booth wrote: > guestconv is not intended to completely replace virt-v2v. Broadly > speaking, virt-v2v does 2 things: > > 1. Move guests between 2 hypervisors. > 2. Make changes to the guest required for a new hypervisor. > > The second is unique to virt-v2v, the first has other tools out there. > guestconv will only

On Wed, Nov 8, 2017 at 9:33 AM, Rafael Avila de Espindola < rafael.espindola at gmail.com> wrote: > Rui Ueyama <ruiu at google.com> writes: > > >> If you are creating an executable and if your executable is not > >> > position-independent, you're using Initial Exec model by default > which is > >> > as fast as variables accessed through

On Sun, 04 May 2008 16:05:44 +0000, Hendrik Boom wrote: > The languages I'm faced with compiling in the near future have nonlocal > go to statements and nested procedures. > > A procedure gets implemented as a structure containing its entry point > and an environment pointer. It is easy enough to call its entry point > and pass the environment pointer as an extra argument

The current Shorewall release model has the following characteristics: a) The last two major releases are supported. b) Only the latest major release is actively developed. c) Bug fixes are available for the prior major release but only against the last minor release. d) The last major release is advertised as the "Current Release". I''m thinking of switching to a model that

On 2020-11-12, Alexander Yermolovich wrote: >Thanks for feedback. > >I agree with patch and numbers this will be a more concrete discussion, but I wanted to judge overall receptiveness to this approach and see maybe there was a better way. > >"Whilst the majority of objects will only have a single CU in them, there will be exceptions (LTO-generated objects, -r merged objects

...nking for DWARF you could encode the 64-bit/32-bit state in there, possibly the section variant (info/rnglists/line etc) and the DWARF version too), on the understanding that consumers like the linker wouldn't combine sections in a potentially broken way. This has the advantage that it could be retrofitted to the existing standard versions, but as has been pointed out, this won't help those with linker scripts - that could only be solved with a new DWARF standard and separate names for 64/32 bit sections, at least if we wanted to avoid the linker needing to do anything beyond reading the section...

Hi all, I have an interesting one - Solaris uses a lot of commands to configure specific items. A simple example is coreadm. In this example: # coreadm -p "/var/core/core_%n_%f_%u_%g_%t_%p" will set the directory and filename to dump core files (with some expansion). The question is - how to get this to run only if the config has changed. I have come up with 2 options, neither of

...nking for DWARF you could encode the 64-bit/32-bit state in there, possibly the section variant (info/rnglists/line etc) and the DWARF version too), on the understanding that consumers like the linker wouldn't combine sections in a potentially broken way. This has the advantage that it could be retrofitted to the existing standard versions, but as has been pointed out, this won't help those with linker scripts - that could only be solved with a new DWARF standard and separate names for 64/32 bit sections, at least if we wanted to avoid the linker needing to do anything beyond reading the section...