similar to: Stripping Debug Locations on cross BB moves, part 2 (PR31891)

On Wed, Feb 8, 2017 at 9:36 AM Adrian Prantl <aprantl at apple.com> wrote: > > > On Feb 8, 2017, at 9:25 AM, David Blaikie <dblaikie at gmail.com> wrote: > > > > So Reid came across a case where the current strategy (dropping > locations when they move across basic blocks) proves to be at odds with > another precept we have: inlinable calls must have

On Wed, Feb 8, 2017 at 9:56 AM Adrian Prantl <aprantl at apple.com> wrote: > On Feb 8, 2017, at 9:44 AM, David Blaikie <dblaikie at gmail.com> wrote: > > > > On Wed, Feb 8, 2017 at 9:36 AM Adrian Prantl <aprantl at apple.com> wrote: > > > > On Feb 8, 2017, at 9:25 AM, David Blaikie <dblaikie at gmail.com> wrote: > > > > So Reid came

On Wed, Feb 8, 2017 at 10:32 AM Adrian Prantl <aprantl at apple.com> wrote: > On Feb 8, 2017, at 10:17 AM, David Blaikie <dblaikie at gmail.com> wrote: > > > > On Wed, Feb 8, 2017 at 9:56 AM Adrian Prantl <aprantl at apple.com> wrote: > > On Feb 8, 2017, at 9:44 AM, David Blaikie <dblaikie at gmail.com> wrote: > > > > On Wed, Feb 8, 2017 at

> On Feb 9, 2017, at 4:09 PM, Robinson, Paul <paul.robinson at sony.com> wrote: > > Sorry to be late to the party, I was out yesterday. > > I do want to point out that there are different motivations for the two cases. When moving/hoisting a single instruction, the motivation is to avoid bad debugger stepping and bad sample-profile data (we get a lot of complaints about

Hello, some misc. cleanup patches for speexdsp, nothing big I'm not sure about how to submit patches, so this is a test balloon :) ultimately, I'd like to fix the FIXED_POINT issue, see http://lists.xiph.org/pipermail/speex-dev/2013-December/008465.html currently, I think the only way to find out how speexdsp has been compiled is to resample some bytes and observe the output; which is

This patch-series implements the ARB_viewport_array for nvc0 and does a little house-cleanig afterwords. V2: Add Release-Notes, mark this in GL3 as done for nvc0 Don't mark the scissors dirty when we don't need to do that Tobias Klausmann (3): nvc0: implement multiple viewports/scissors, enable ARB_viewport_array docs: update GL3.txt, relnotes: mark GL_ARB_viewport_array as done

On Tue, Apr 15, 2014 at 12:33 PM, Peter Meerwald <pmeerw at pmeerw.net> wrote: > Signed-off-by: Peter Meerwald <pmeerw at pmeerw.net> > --- > libspeexdsp/resample.c | 14 +++++++------- > 1 file changed, 7 insertions(+), 7 deletions(-) > > diff --git a/libspeexdsp/resample.c b/libspeexdsp/resample.c > index e32ca45..a19b997 100644 > ---

This patch-series implements the ARB_viewport_array for nvc0 and does a little house-cleanig afterwords. Tobias Klausmann (3): nvc0: implement multiple viewports/scissors, enable ARB_viewport_array nvc0: mark scissor in nvc0_clear_{} nv50/ir: Remove NV50_SEMANTIC_VIEWPORTINDEX and its last consumer .../drivers/nouveau/codegen/nv50_ir_driver.h | 1 -

Has anyone made, or have any simple PHP, or HTML interfaces where by a user could enter their number and the number they want to call, and have asterisk bridge the calls?

Hi, I intended to file this bug on Bugzilla, but I've received no response from llvm-admin in the 10 days since asking for a Bugzilla account. I've written 2 test functions in C that take in a float array x of size n and output float array f(x), where f is either fabsf or logf. The LLVM 3.9 auto-vectorization docs claim that both functions will be vectorized:

Functionally identical but much simpler. Should also better integrate with future layer/viewport changes/fixes. Cc: 10.1 <mesa-stable at lists.freedesktop.org> Signed-off-by: Ilia Mirkin <imirkin at alum.mit.edu> --- Not *strictly* necessary in stable, but it will make backporting later fixes easier. No regressions in piglit. src/gallium/drivers/nouveau/nv50/nv50_program.c | 5

+Tanya for the account issue. > On Oct 27, 2016, at 11:36 AM, Eric Martin via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > Hi, > I intended to file this bug on Bugzilla, but I've received no response from llvm-admin in the 10 days since asking for a Bugzilla account. > > I've written 2 test functions in C that take in a float array x of size n and output

Eric, I apologize for any delay or confusion. From my records/list archives, I saw that Anton had created an account for you on Oct 17th and responded to your email to llvm-admin. I am not sure what happened after that point as I thought the account was done. I just confirmed there is an account for you in bugzilla, so you should be good to go if you reset your password. -Tanya > On Oct 27,

Hi Everyone, I am trying to pass a variable using the .call files but it turns out blank. Can someone please point out what might be wrong here: */tmp/spool-file.sh* *----------------------------------------------------------------------* echo "Channel: Local/s at callback_leg*1*/n CallerID: \"Call-back\" <123456> MaxRetries: 0 RetryTime: 10 WaitTime: 45 Context:

Hi lists, Sorry for cross-posting, but these two patches are of concern to clang and llvm. I'm compiling C-code which includes inline assembler which looks like the following using the sparc-target: static inline float fabsf(float a) { float res; __asm __volatile__("fabss %1, %0;" : "=f"(res) : "f"(a)); return

Chris Lattner wrote: > The way to deal with this is to add LLVM intrinsics, but only for > functions that set errno. For example, you could add llvm.sqrt, which > is just undefined on a negative value other than -0.0. For your uses, > you just emit llvm.sqrt, the C frontend will make use of it and wrap > errno handling around it as required. > > For functions like

Hi Patrick, I do not see a problem with those patches --- apart from missing tests ;) Cheers, Arnaud On Mon, Mar 21, 2016 at 3:11 PM, Patrick Boettcher via cfe-dev < cfe-dev at lists.llvm.org> wrote: > Hi lists, > > Sorry for cross-posting, but these two patches are of concern to clang > and llvm. > > I'm compiling C-code which includes inline assembler which looks

Hello, I have been gone for a while, finishing work on my Master's thesis... Now that I'm back I updated LLVM to the most recent version and found that my FP_ABS SelectionDAGNode type and code generation was now conflicting with the new FABS node type. I brought the rest of my local modifications in line with the FABS implementation, so here is my patch that includes sqrt, sin and cos

I would like to suggest a slight modification to diag(). In the case where x is a matrix with both row names and column names the same, it would be reasonable if the resulting vector also had those names. I often use diag() on variance matrices, where this modification is helpful. The modification requires replacing if (is.matrix(x) && nargs() == 1) return(c(x)[1 +

Hi Everyone, Can I suggest a couple of new `codes' methods. I know codes is a bit dodgy (at least, according to the comments in codes.factor), but for what it's worth I like to extract codes from data frames of factors, for which the following two functions (which operate recursively) are helpful: "codes.default" <- function(x) { if (is.list(x)) lapply(x, codes)