search for: hacky

Hi, On 14-03-16 16:05, Ilia Mirkin wrote: > There's a less hacky and more hacky way forward. The more hacky solution is > to set file index to -1 or something and then not do the lowering when you > see that. > > The less hacky solution is the one you proposed as #1 - introduce a new > file for "buffer" memory and lower it to the global...

...I put an #ifdef around the logic in py_guestfs_mount_9p and py_guestfs_list_9p, I.e. Left the signatures but the functions just return a a NULL PyObject. It now builds and installs with pip. Thanks for all your help most appreciated. Is there a better way to do this?, #ifdefs always seem a little hacky. Regards John On 9/14/15, 12:47 PM, "Richard W.M. Jones" <rjones@redhat.com> wrote: >On Mon, Sep 14, 2015 at 07:06:48PM +0000, John McDowall wrote: >> Richard, >> >> It is looking better, but still getting error - see attached log. >> >> I remov...

Amara, first, thank you for answering. but I found expandPsuedo instructions actually happens before post-RA, like the following code showing: your approach is a little hacky, right? : ) // Expand pseudo instructions before second scheduling pass. addPass(&ExpandPostRAPseudosID); printAndVerify("After ExpandPostRAPseudos"); // Run pre-sched2 passes. if (addPreSched2()) printAndVerify("After PreSched2 passes"); // Second pass sche...

...y common concern about the naming of ''presence'' . Instead of changing the behaviour of the presence validator, I was wondering if maybe the answer to avoid such misconceptions could be to create a new validator called presence_of_boolean that abstracts the sometimes called "hacky" validates_inclusion in: [true, false] What do you guys think? Sergio Campamá -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To unsubscribe from this group and stop receiving emails from it, send an email to rubyonrails-c...

Hi, On 14-03-16 16:41, Samuel Pitoiset wrote: > > > On 03/14/2016 04:28 PM, Hans de Goede wrote: >> Hi, >> >> On 14-03-16 16:05, Ilia Mirkin wrote: >>> There's a less hacky and more hacky way forward. The more hacky >>> solution is >>> to set file index to -1 or something and then not do the lowering when >>> you >>> see that. >>> >>> The less hacky solution is the one you proposed as #1 - introduce a new >>&...

This little "hack" fixes the use of OpenCL global memory buffers with nouveau, but clearly the #if 0 is not a solution as it breaks buffers with GLSL. The reason I'm posting this as an RFC patch is to discuss how to solve this properly, 2 solutions come to mind: 1) Use separate nv50_ir::FILE_MEMORY_xxx values for buffers versus TGSI_FILE_MEMORY with TGSI_MEMORY_TYPE_GLOBAL,

What I meant was to write your own expansion pass and run it after the scheduler passes, e.g. in the pre-emit stage. > if (addPreEmitPass()) printAndVerify("After PreEmit passes") Though if it's too hacky for you then fair enough. Amara On 23 November 2013 03:17, Liu Xin <navy.xliu at gmail.com> wrote: > Amara, > > first, thank you for answering. but I found expandPsuedo instructions > actually happens before post-RA, like the following code showing: > your approach is a litt...

There's a less hacky and more hacky way forward. The more hacky solution is to set file index to -1 or something and then not do the lowering when you see that. The less hacky solution is the one you proposed as #1 - introduce a new file for "buffer" memory and lower it to the global file by adding a base of...

...Emerson <amara.emerson at gmail.com>wrote: > What I meant was to write your own expansion pass and run it after the > scheduler passes, e.g. in the pre-emit stage. > > if (addPreEmitPass()) > printAndVerify("After PreEmit passes") > > Though if it's too hacky for you then fair enough. > > Amara > > On 23 November 2013 03:17, Liu Xin <navy.xliu at gmail.com> wrote: > > Amara, > > > > first, thank you for answering. but I found expandPsuedo instructions > > actually happens before post-RA, like the following code...

...n opt (or build your own pass-by-pass harness), and then run "the > passes you want on it" instead of "trying to stop certain passes from doing > things to it". > True, but why would you want to force that speed bump onto other developers? I'd argue that's more hacky than the inline asm. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20151103/ce6d1a5c/attachment.html>

On 03/14/2016 04:28 PM, Hans de Goede wrote: > Hi, > > On 14-03-16 16:05, Ilia Mirkin wrote: >> There's a less hacky and more hacky way forward. The more hacky >> solution is >> to set file index to -1 or something and then not do the lowering when >> you >> see that. >> >> The less hacky solution is the one you proposed as #1 - introduce a new >> file for "buffer&qu...

Hi Arpith, That is exactly what it is :). My bad, I thought I copied over the libraries to where LIBRARY_PATH pointing but apparently it was copied to a wrong destination. Thanks a lot. On Wed, Jan 20, 2016 at 4:51 AM, Arpith C Jacob <acjacob at us.ibm.com> wrote: > Hi Ahmed, > > nvlink is unable to find the GPU OMP runtime library in its path. Does > LIBRARY_PATH point to

...s with Nouveau as well. > > Also what was the issue being solved here? No references to any bugs and not > even explaining any issue at all isn't the way we do things. > > And even if it means a muxed design, then the fix is to make it work inside the > driver, not adding some hacky workaround through ACPI tricks. > > And what out of tree drivers do or do not support we don't care one bit anyway. > I think the reverts should be merged via Rafael's tree as the original patches went in via there, and we should get them in asap. Acked-by: Dave Airlie <airlie...

In the following example, for some reasons, the input pointer entering the loop was casted to generic pointer. How can the backend get rid of the addrspacecast and use local store in the loop? for.body.lr.ph: ; preds = %entry %0 = addrspacecast i32 addrspace(3)* %in to i32 addrspace(4)* br label %for.body for.body: ; preds = %for.body, %for.body.lr.ph %i.03 = phi i32 [ 0, %for.body.lr.ph ],

...will assign a new IP for the host. Is there any configuration variable we could use to avoid HWaddr changing? Currently, I have added a short snippet into tinc-up script that persists the (once given) HWaddr to a file and tries to reset it before starting dhclient. This works, but I feel it a bit hacky solution... -- tinc-up -- #!/bin/sh set -e MACFILE="/etc/tinc/mynet/mac" if [ -e $MACFILE ]; then MAC=`cat $MACFILE` ifconfig $INTERFACE hw ether $MAC fi dhclient $INTERFACE & MAC=`ip link show mynet | awk '/ether/ {print $2}'` echo $MAC > $MACFILE -- tinc-up ends...

...r, exactly here: glxExtensions = glXQueryExtensionsString (dpy, screenNum); if (!strstr (glxExtensions, "GLX_EXT_texture_from_pixmap")) The issue is, glXQueryExtensionsString won't return texture_from_pixmap on AIGLX if LIBGL_ALWAYS_INDIRECT isn't set. Now, the hacky solution would be to do something like the patch I attached to the bug 8160. The proper solution would probably to add an optional parameter to glXQueryExtensionsString to force indirect rendering. Shouldn't be that hard, some fiddling around with stdarg/va_list. As this probably results in...

On 03/14/2016 08:50 PM, Hans de Goede wrote: > Hi, > > On 14-03-16 16:41, Samuel Pitoiset wrote: >> >> >> On 03/14/2016 04:28 PM, Hans de Goede wrote: >>> Hi, >>> >>> On 14-03-16 16:05, Ilia Mirkin wrote: >>>> There's a less hacky and more hacky way forward. The more hacky >>>> solution is >>>> to set file index to -1 or something and then not do the lowering when >>>> you >>>> see that. >>>> >>>> The less hacky solution is the one you proposed as #1 - i...

...s.id LEFT OUTER JOIN `key_factors` ON key_factors.trait_value_id = trait_values.id WHERE (trait_values.trait_id = traits.id AND key_factors.id = key_factors.id) Now that final join clause needs to be specified slightly differently (it needs another condition) - this is where it get''s hacky. Various experimentation in trying to solve this problem showed that the association based includes are specified before anything in a joins field, AND the contents of the joins field is directly appended. So, the relevant condition can be specified there, and it will be appended to the auto-genera...

> No, non-sideeffecting operations can be legalized as compiler-rt calls Right, but not as "regular" nodes with side-effects? I guess you could search and analyze the DAG manually but that seems hacky. Maybe something that one day LLVM could support natively. On Thu, Jul 16, 2020 at 11:55 AM Matt Arsenault <arsenm2 at gmail.com> wrote: > > > On Jul 16, 2020, at 14:47, Hendrik Greving <hgreving at google.com> wrote: > > I think their originating node already has a cha...

...should work; actually it did work for many years... > > Your just proposed change was my first attempt for solving this but for some > reason it did not work. After testing a lot the only way I've found to solve this > bug was defining a "real" empty function. I know, 100% hacky but it works. If the voiding doesn't work, we'll need that function in another 44 lines of code, spread throughout the source. -- -Gene